What approaches have you tried? Is the complicated backend process itself written in node?
This sounds like a good use for child_process.spawn. You could keep track of how many instances are running easily if there is a single web interface node process, or with a little more work if you need to use an external scoreboard like redis. On Tuesday, September 1, 2015 at 8:27:16 AM UTC-4, Dirk Hoving wrote: > > Hi, > > We are trying to cluster a level deeper than is usual. > > NodeJS seems to developed to be able to run a code than can be accessed by > multiple users and every instance can be run by a different worker. > > Now we have a case, where we have only one user with a very complicated > backend process. This single instance of the code causes the CPU to > overload at times so we want to split up the work over different CPU cores. > We have tried multiple approached but haven't been able to make it work > yet, any insight to this? > > Thanks, Dirk > -- 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/f58103f9-63ba-45ee-88b5-ed70e88c0200%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
