Thanks for the good explanation.
Can I request that the message be more end user friendly?
At the moment it tells the poor user that this application is out of
grunt and how to get more grunt, but they don't really care about that
- _they_ aren't the ones who are going to be buying more dynos.
In my honest opinion this message should never be presented at all.
I'd rather have a generic too many concurrent connections message
presented to the user, along with a detailed email to the owner.
Furthermore, in your application management page you should have a
log / history, with detailed
Not sure if you need to edit your code.
heroku restart
sounds like a good place to start :)
GaJ
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Heroku group.
To post to this group, send email to
I get this error for http://home-fogboundpictures.heroku.com/
Heroku | Backlog too deep
The application currently has too many requests in its backlog. If you
are the application owner, see http://docs.heroku.com/performance for
information on how to avoid this timeout.
That's fine, but when
This doc is in the works right now, thanks for giving us a friendly
nudge on getting it finished. :)
In the meantime, here's a rough cut of the explanation:
The backlog is the number of requests waiting to be processed. If
you're using the default (one dyno), it can only process one request
at
That was a good explanation and would make a good addition to the
docs. So what is the difference between a dyno and a compute unit?
Carl
On Mon, May 25, 2009 at 3:58 PM, Adam Wiggins a...@heroku.com wrote:
This doc is in the works right now, thanks for giving us a friendly
nudge on getting
