Another nasty consequence being that Heroku’s 30s request time limit, which used to be based on request time alone, is now based on request AND queue time. Which means that a fast request, taking say 2s, could still trigger an “H12” timeout error if it gets caught in a large queue at a dyno.

Which is exactly what happens – in our case, more than than a thousand times an hour.

This video is processing – it'll appear automatically when it's done.

This video is processing – it'll appear automatically when it's done.

As described on this page

This video is processing – it'll appear automatically when it's done.

This video is processing – it'll appear automatically when it's done.

This video is processing – it'll appear automatically when it's done.

From the Wayback Machine!

This video is processing – it'll appear automatically when it's done.

This video is processing – it'll appear automatically when it's done.

a.k.a. Apache Bench

This video is processing – it'll appear automatically when it's done.

This video is processing – it'll appear automatically when it's done.

They even wrote a success story about us:

This video is processing – it'll appear automatically when it's done.