[amatix]

From the article, it sounds like they were well aware of the logs & queue values, but they were misleading:

Their logs are STILL incorrect. Here’s a sample line:

  2013-03-02T15:41:24+00:00 heroku[router]: at=info method=GET path=/Asap-rocky-pretty-flacko-lyrics host=rapgenius.comfwd="157.55.33.98" dyno=web.234 queue=0 wait=0ms connect=3ms service=366ms status=200 bytes=25582

Those queue and wait parameters will always read 0, even if the actual value is 20000ms. And this has been the case for years.

[sologoub]

Interesting... just ran my own test and looks like I have jumped to conclusion too fast. NewRelic and the queue data do not seem to match, so I have some more reading to do.