3 ms·
Funny, I was thinking a web app is ideal for thread per core. The application itself generally has very little state outside of a request (other than for the so
by ndriscoll 3y ago
Funny, I was thinking a web app is ideal for thread per core. The application itself generally has very little state outside of a request (other than for the socket listener and database connections, which can be segmented per thread), and what state it has is probably mostly static across requests (so caches don't invalidate often). It should be easy to deal with ownership of shared state because there isn't any.
- cmrdporcupine 3y agoIt all depends on if you think the operating systems scheduler is better than your async framework's. There's a long tradition of not wanting to "waste" threads by blocking on I/O.