On a side note, I just read the fully-loaded article and it dismisses node's cluster module this way ...
---- quote ---- Approach 4: Use node’s cluster module! NodeJS 0.6.x and up offer a cluster module which allows for the creation of processes which “share a listening socket” to balance load across some number of child processes. What if you were to combine cluster with one of the approaches described above? The resultant design would inherit the shortcomings of synchronous or internally threaded solutions: which are not responsive and lack grace. Simply spinning new application instances is not always the right answer. ---- end quote ---- This seems unfounded. Why don't extra processes help? He makes the claim it's no better but doesn't explain why. I've used multiple processes in the past and it worked great. . -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
