> 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. >
This may depend on how node-core interfaces with the socket library. If a C++ thread is calling accept() on incoming sockets while you are blocking the main loop with your computation, you will have a bunch of queued requests that do not get fulfilled by a non-busy processes. If however accept() is only called once per tick, you shouldn't have outstanding requests in waiting. I think the solution to any CPU intensive task is a work queue. Do not mix your IO-bound processes with your CPU-bound processes. Node doesn't suck at CPU-bound tasks, it just can't do IO at the same time. It's not like a threaded app will magically have more CPU to compute with. -- -- 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 [email protected] To unsubscribe from this group, send email to [email protected] 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
