Re:Node.js memory benchmark confirms V8's GC may not be read...
by xearl on Wednesday September 29, 2010 @12:02PM
(#1739893)
You're interpreting the graph incorrectly. There's no "bottom of the curve", the graph is showing a distribution, not some property over time. A correct reading will e.g. tell you that out of 50'000 requests a total of ~30'000 requests completed in 100ms or less. Or similarly for what you call the bottom of the curve: 5'000 out of 50'000 requests complete in ~25ms or less. This does _not_ state which 5'000 requests that were, and in particular it does _not_ imply that the _first_ 5'000 requests are faster. For this you'd have to plot response time over time.
Re:Node.js memory benchmark confirms V8's GC may not be read...
by jiaaro on Thursday September 30, 2010 @03:12PM
(#1744442)
ahh... For some reason I thought it was showing request volume
Re:Node.js memory benchmark confirms V8's GC may not be read...
by maushu on Wednesday September 29, 2010 @11:37AM
(#1739784)
It is recommended to use multiple node processes on multi-core servers since node is single-threaded.
Re:Node.js memory benchmark confirms V8's GC may not be read...
by felixge on Wednesday September 29, 2010 @12:35PM
(#1740031)
That will help with the symptoms, but not with the problem. Having big response-time variations like this is undesirable.
Re:Node.js memory benchmark confirms V8's GC may not be read...
by maks on Thursday September 30, 2010 @07:44PM
(#1745323)
Not only that, but one of Node's big selling points has been the supposed flat response time distribution it achieves with a simple 'helllo world' example.
Clearly thats not the case once each Node/V8 need to do a real-world amount of work per request.
Can the performance issues be solved by adding hardware? (or spin up more node processes so that each one stays at the bottom of the curve?