News for hackers. Stuff that matters.
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.