On Saturday, January 3, 2015 1:21:05 PM UTC-5, Peter Frazier wrote: > > Good morning|afternoon|evening, > > the issue i'm running into is the code seems to just stop at a > Article.findOne() mongoose call. any and all console.log()'s never fire. > Is there some limitation? http://jsapp.us/s/515 is a link to the code.. > > is there limitations in queuing and saves databases? Am I using processes > wrong? > > I don't see where you are spawning processes at all in this code. Without that part it is difficult to say what might be going wrong.
Does this code work fine if you do it without spawning processes? What benefit, exactly, do you hope to get by spawning processes? Are the tasks CPU-intensive, so you're spinning your wheels in JavaScript and not answering new requests? If every API request sooner or later winds up hitting this code, then there's no real benefit in responding to requests faster than you can actually process them. Our approach in this situation is to run multiple independent copies of the application, no more than one per core usually, listening on separate ports, and use nginx as a round-robin load balancer, which is very easy to set up and a proven solution. -- 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/f120d279-9a77-4759-bce9-0ec33233c79f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
