If this is the case then I should remove http caching in order to prevent the app from shutting down as much as possible. But... why requesting a cached page starts the app if the request is never handled by the app?
On Jan 7, 11:18 am, Steve Smith <[email protected]> wrote: > I'm not an expert on this so I would double check, however I think this is > all the case, > > If you only have one dyno then the app will shutdown when there are no > requests for a certain time period. I believe this isn't the case once you > have more than one dyno but in my experience at that point you have enough > concurrent connections to keep things alive anyway. > > If you are caching the page it will be stored in varnish so the request will > never be handed out to the app and will therefore allow the app to shutdown. > > Steve > > On 7 Jan 2011, at 09:02, Martin Petrov wrote: > > > > > > > > > Hi, > > > Looking at my logs I see that if my application is not used for 1 hour > > its state is changed from up to down. Next time a request comes it > > takes several seconds to start again. > > > Does requesting an http cached page keeps the application alive? My > > app has only one page, which is http cached. > > > -- > > You received this message because you are subscribed to the Google Groups > > "Heroku" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]. > > For more options, visit this group > > athttp://groups.google.com/group/heroku?hl=en. -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
