News for hackers. Stuff that matters.

A comment on The Unscalable, Deadlock-Prone, Thread Pool. Parent comment

Re:The Unscalable, Deadlock-Prone, Thread Pool by felixfbecker on Wednesday February 27, 2019 @07:23AM (#19262775)
This is a common misconception. Node (libuv) only uses the thread pool as a last resort. Many operations nowadays have a native async OS API, so they don't need to use (and therefor don't block/fill) the thread pool.

https://medium.com/the-node-js-collection/what-you-should-kn...

https://stackoverflow.com/a/22644735/4208018

[ Parent | on HN ]
Re:The Unscalable, Deadlock-Prone, Thread Pool by jorangreef on Wednesday February 27, 2019 @07:38AM (#19262841)
"Node (libuv) only uses the thread pool as a last resort."

When did you last read deps/uv/src/win/fs.c or deps/uv/src/unix/fs.c?

If by "last resort" you mean 99.9% of all async fs tasks, then I would agree with you.

[ Parent | on HN ]
Re:The Unscalable, Deadlock-Prone, Thread Pool by coder543 on Wednesday February 27, 2019 @11:48AM (#19264457)
isn't that because OSes have broken async filesystem APIs that can't be trusted?

But network requests (like dns) have well defined APIs for async, and should never be required to block a thread, and therefore do not need a threadpool.

[ Parent | on HN ]