|
|
|
|
|
by monkeyelite
409 days ago
|
|
> Linux in particular has invested heavily in this, from select, to poll, to epoll, and now unto io_uring. Correction. People who wanted to do async IO went and added additional support for it. The primary driver is node.js. > And they have simply not been optimized with this kind of scale in mind, yes, processes do not sacrifice security and reliability. That’s the difference. The fallacy here is assuming that a process is just worse for hand wavy reasons and that your language feature has fa secret sauce. If it’s not context switching then that means you have other scheduling problems because you cannot be pre-empted. > There's a reason typical ulimit configurations are limited to around 1000 threads/processes per system STILL waiting to hear about your experience of maxing out Linux processes on a web server - and then fixing it with green threads. I suspect it hasn’t happened. |
|