Re:Napa.js: A multi-threaded JavaScript runtime
by skosch on Wednesday October 18, 2017 @09:53AM
(#15499131)
That's why the post you just replied to suggested that Node may not be the right tool for those kind of tasks.
Re:Napa.js: A multi-threaded JavaScript runtime
by kelnos on Wednesday October 18, 2017 @06:28PM
(#15503814)
The problem is that I see a lot of projects written in languages with single-threaded runtimes (python more often than node) that become difficult/expensive to scale and extend down the road. I loathe the idea of a rewrite, but sometimes the initial language choice lacked forethought to the point where it makes sense to rewrite in something that actually can make use of all of a machine's processing resources.
Things like greenlet and gevent (and likely napa.js) are band-aids over the underlying problem.
Re:Napa.js: A multi-threaded JavaScript runtime
by grawlinson on Wednesday October 18, 2017 @05:41PM
(#15503437)
For these workloads, I would consider a compiled language with great parallelism/concurrency. e.g Rust or GoLang.
Think about something like Delaunay triangulation or mesh refinement. These are critical path bottlenecks for a great many applications and in practice very parallel, but they're irregular so we cannot easily distribute the data structure. The best results we have are for shared memory thread models. We don't know how to do it any other way!