Thanks for all the replies, lost the topic so didn't reply back earlier. It is a case where only server side is running (one instance that does a lot of calculations on data it retrieves from websites and performs actions based on these calculations (e.g. database entries or other asynchronized requests)).
One good solution we have found is to start up different parts of the code in another node.js instance and have the several node.js instances communicate with each other over sockets internally. On Tuesday, September 1, 2015 at 2:27:16 PM UTC+2, 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/38d64f06-6277-477b-813b-5f6e1d10b3e7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
