child_process.fork creates a new node.js process with this specifcs: "These child Nodes are still whole new instances of V8. Assume at least 30ms startup and 10mb memory for each new Node. " from here: http://nodejs.org/api/child_process.html#child_process_child_process_fork_modulepath_args_options. they are no threads. so in the embedded environment i'd look for a solution without many forks.
witch loading time being critical i'd got for creating all nodes on startup once and let them act as services. On Thursday, June 5, 2014 5:30:30 AM UTC+2, Vinay Ram wrote: > > I have a scenario where multiple node apps must be executed in embedded > environment. Loading time is one of the crucial factor and I am wondering > if running the apps in separate child processes (using child_process.fork) > is faster than running them in independent node processes. Any ideas? > > A related question. Does child_process.fork() use copy-on-write? > -- Job board: http://jobs.nodejs.org/ New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md Old group rules: 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 unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/1f536ee2-26ab-41b1-b96d-157cd557a057%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
