3 ms·
> is heavily multithreaded (typically 20-60 threads) Hm. For me "heavily multithreaded" is 1000 threads and more. That said, I just detach them, there's no rea
by otabdeveloper4 5y ago
> is heavily multithreaded (typically 20-60 threads)
Hm. For me "heavily multithreaded" is 1000 threads and more. That said, I just detach them, there's no real reason to wait for a thread.
- PaulDavisThe1st 5y agounless you've got 1000 cores OR are severely i/o bound, 1000 threads seems mostly useless. OTOH, "severely i/o bound" tends to describe client/server computing quite well, so maybe that's just what you need. my stuff isn't client/server computing, my threads are generally compute bound, and having (lots) more than there are cores would be counter-productive.
- otabdeveloper4 5y ago1000 threads blocking on I/O operations is the same as an epoll() over 1000 file descriptors under the hood, except you also get pre-emption guarantees from the kernel. Yeah, so basically this. Except that "I/O bound" usually implies critical moments of computation too, and pre-emption is really nice here.