4 ms·
Disk I/O I can definitely believe, but not every request from the DB goes to disk right? especially for in-memory databases Also, I can NEVER explain evented s
by hardwaresofton 13y ago
Disk I/O I can definitely believe, but not every request from the DB goes to disk right? especially for in-memory databases
Also, I can NEVER explain evented servers adequately when people ask me about them. Especially how an evented server like twisted or tornado or gunicorn work when run from inside python (struggling w/ the GIL). But yes, I didn't even consider that -- all the stuff is synchronous! Amazing that they can handle so many requests with little to no hiccups
- crucialfelix 13y agoThe issue is that while many requests are very fast to serve from cache, they can get blocked if your limited number of workers get caught handling long ones. If an admin is using a rarely used and inefficient page, or a few too many people are uploading lots of images at once. I have 400 real estate agents, and if they happen to all want to edit their listings at the same time then the customers get frozen out. Varnish would help here.