3 ms·
The README expained it clearly > As it evolves, we find it useful to complement Node.js in CPU-bound tasks, with the capability of executing JavaScript in mult
by chenzhekl 9y ago
The README expained it clearly
> As it evolves, we find it useful to complement Node.js in CPU-bound tasks, with the capability of executing JavaScript in multiple V8 isolates and communicating between them.
Not everything MS did was evil.
- couchand 9y agoIt's not evil it's just dumb. If your workload is CPU bound you probably shouldn't be running it in Node.js.
- fenwick67 9y agoThere are some cases on the threshold that this can be useful for. For example, let's say your Node application's requirements changed, and now you have to transform a set of five JSON objects to one JSON object, with some big arrays, indexing, and sorting required. The operation takes 10-100ms of cpu time, which isn't nuts, but with thousands of requests per second would normally be a catastrophe. If you can spawn a thread in this case you can save the day.
- couchand 9y agoYou say that 10-100ms of CPU time on the hot path of your requests isn't nuts, but we'll just have to agree to disagree about that.
- fenwick67 9y agoAll I meant was "transforming and merging complex documents can really take this much time", not "stopping your whole server application for this long is okay" (that would be nuts).