On Fri, Jan 3, 2014 at 1:47 PM, Johan Alkstål <[email protected]>wrote:
> > So should this forked child process always be running (and thus having all > simulations use it) or should I fork one for each simulation run? > > I mean if the simulations should be queued and executed in order or in > parallel by multiple processes? > That'll depend on how long these simulations run and how many of them there will be - but I would suspect you want on child process per simulation. > And what are the benefits/drawbacks from using the web worker > implementation with multiple threads? > Web worker is just a different (browser compatible) API for child_process.fork. Probably you should just use the API node provides unless you're thinking about running these simulations client side as well. -- -- 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.
