undefined | Better HN

0 pointsstingraycharles8y ago0 comments

Assuming everything you do is non-blocking, this effectively means a container per core.

Not ideal, but not too bad either.

0 comments

2 comments · 1 top-level

stupidcar8y ago· 1 in thread

And if it isn't non-blocking? What if I'm writing a game and want to run parts of the rendering, AI, physics, etc. in parallel? Do I create a bunch of containers for each subsystem of my game and have them all communicate via IPC? This doesn't sound like a recipe for good memory/performance characteristics.

stingraycharlesOP8y ago

But we’re talking about javascript here, a language that is async about almost everything.

I completely agree with what you’re saying for those other problems you describe. But for the typical node.js webapp, doing the one-container-per-core is perfectly fine.

j / k navigate · click thread line to collapse