Hello Dirk, I dont want to sound rude, but you provided rather little detail, leaving us with barely anything to work with. I myself have had clustering issues, and there are a variety of things you can do - spreading from using RPC methods like hprose over to using a cluster solution like SocketCluster or PowerHouse, over to simply running the more independent parts as separate child_process.spawn’s.
The more you can tell, the better we can answer :) Kind regards, Ingwie. On Di. Sep. 01 2015 12:45:43 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/4B9F074A-41F8-472F-821E-642A05824E98%40googlemail.com. For more options, visit https://groups.google.com/d/optout.
