You can also take a look at https://github.com/xk/node-threads-a-gogo
It gives you in-process threads to which you can delegate the CPU intensive tasks. On Friday, June 29, 2012 3:33:32 PM UTC+2, hd nguyen wrote: > > Thanks for your help and explanation. > Everything is quite clearer to me :) > > On Fri, Jun 29, 2012 at 8:27 PM, Bradley Meck <[email protected]>wrote: > >> Usually people use worker pools so they don't spawn up a new process per >> request. The moving of heavy computation to other processes has various >> advantages and pitfalls ( computation crash for w/e reason can be dealth >> with, but data must be sent via IPC usually, etc ). >> >> I would spawn up a ton of worker processes at the start of your app and >> if you need more spawn more as a flexible pool. >> >> -- >> 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 >> > > > > -- > Nguyen Hai Duy > Mobile : 0914 72 1900 > Yahoo: nguyenhd_lucky > -- 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
