4 ms·
A Node.js library to run CPU-intensive tasks and not block the event loop
- tracker1 9y agoVery cool... this could be extremely useful to me. I've been doing a fair amount of ETL work, and quite a bit of it could be more parallel.
- BinaryIdiot 9y agoAny reason this doesn't use the cluster API? As far as I can tell it uses `child_process` but `cluster` could accomplish the same thing, easier, and it's what it is meant to do.
- stevenmays 9y agoHow is this superior to clustering? https://nodejs.org/api/cluster.html https://nodejs.org/api/cluster.html
- tbrock 9y agoThey are different. Clustering is useful for when the requests have roughly the same cost and serves to distribute that load over several cpus roughly evenly (because a NodeJS is single threaded you need this to take full advantage of modern hardware). Workers are useful when requests vary greatly in cost (some far outweighing the others) so that the event loop is not blocked for less costly tasks by much more costly ones. Consider a web application serving http requests. You would want to multiplex those requests over available cpus on a machine with workers but would not want to block processing any of those individual cluster workers with expensive requests.