3 ms·

Those numbers kinda surprised me too. We serve millions of requests per day and have some slow responses (75+ ms) but on any given day our servers handle 175 r

• spimmy 11y ago
  Keep in mind that we're a platform, not a website, and we have very little control over things like schemas, slow queries, inefficient looping requests that our developers send us. We can't optimize 500 thousand apps' queries for them. So for example if an app does something bad like performing a full table scan on every request against a 300 million collection, so every request to that backend is timing out at 30 seconds, and there are thousands of them per second, well -- pretty soon your fixed pool will be full of requests timing out to that backend.
  • rdw 11y ago
    This is totally a great explanation, thanks! This sort of thing is why I hate working on platforms (but also why it's so in-demand).
• spimmy 11y ago
  (we can, and do, do a lot of things to limit the impact any one app can have ... but there are limits. Async is much better for our API model.)