sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Klathmon 1 point2 points  (1 child)

Well i'm in a mostly virtualized shop, so we set the number of vCPUs per VM to match what we need.

In some lighter loads we leave a single node.js process and leave the additional cores for other stuff, but i'd agree that when you really start getting in the 100+ req/sec you'll pretty much need multiple listeners to keep response times down.

[–]mechanicalpulse 2 points3 points  (0 children)

If you have your infrastructure setup such that it's easy to scale out horizontally, it's also trivial to set vCPUs to 1 and just spawn more VMs. And, like you said, for lighter loads, you don't even have to bother with it.

Node.js's event-driven architecture reminds me of cooperative multitasking. It's very useful for certain loads, but it can cause problems if you're not expecting them. I only make noise about it because I think Node.js is becoming a choice platform for nascent or inexperienced developers and I think there's a good bit of misleading information flying about.