> It's a problem for anyone using a web framework/server combo that does't allow for concurrent requests on a single dyno. Or one that allows only k concurrent

> It's a problem for anyone using a web framework/server combo that does't allow for concurrent requests on a single dyno. Or one that allows only k concurrent requests with a routing mesh that schedules m>k per server (dyno) or at least does that often enough. Even with unlimited concurrent requests per server, similar problems may arise if the performance drops sharply with the number of concurrent requests being served (e.g. due to swapping.)