3 ms·
There's two main reasons: * gunicorn doesn't have worker scaling, they're all always running, so async workers were to not waste those resources idling while s
by Izkata 2y ago
There's two main reasons:
* gunicorn doesn't have worker scaling, they're all always running, so async workers were to not waste those resources idling while still allowing lots of simultaneous clients
* The limit was 32768 not that long ago, which was at least possible to hit with a ton of clients
- liontwist 2y agoWhy would I be worried about processes using resources while blocked (not using CPU)? Virtual memory is a thing. And if it’s a web server that’s just not being used.
- Izkata 2y agoRAM, not CPU, which goes right back to this post's benchmark. Python code takes up memory too, not just data. The workers consume this memory on startup, not just while handling a request.