3 ms·
To clarify, node already has parallelized I/O threads. The only thing that isn't parallelized is the JS-land code.
by Animus7 15y ago
To clarify, node already has parallelized I/O threads. The only thing that isn't parallelized is the JS-land code.
- exDM69 15y ago> To clarify, node already has parallelized I/O threads. The only thing that isn't parallelized is the JS-land code. But Node.js runs only in a single native thread, right? So it's single threaded I/O multiplexing using epoll/kqueue and the thread calls JS callbacks when some I/O takes place. In C or C++ you could run n native threads serving m sockets using a single "reactor".
- mnutt 15y agoNode.js only has a single thread for the event loop. (where the user's javascript is run) Internally it uses a thread pool. You could certainly do what you describe and it would be very similar to node's Cluster module, which uses multiple processes. In fact, I believe in the next release they're giving you the option to replace processes with threads under the hood.
- chapel 15y agoThat actually isn't the case anymore. It has been removed for various reasons, a major one is stability. While the promise of isolates was nice, I think the choice to remove them was a good one considering the tradeoffs. More info: https://groups.google.com/forum/?fromgroups#!topic/nodejs/zLzuo292hX0 https://groups.google.com/forum/?fromgroups#!topic/nodejs/zL...