+1000 On Thu, Feb 16, 2012 at 02:34:09PM -0600, John McCaffrey wrote: > Once you pay for a dyno, its up all the time, so this strategy is only > necessary when you are not yet paying to host your site on heroku. > > So I think it makes sense to take the idea of "ping the server every X > min", and add a bit more to the logic of asserting that the response is > correct and timely. Implementing even a basic strategy for monitoring your > application's uptime, performance, and consistent functionality is an > important component in how you manage your site, and there are a variety of > tools out there that can help. > > New relic can ping your app and alert you when it is not responding and > passing your assertion test. (specific words on a page) > > You can have a simple ping and report from http://www.internetvista.com > > BrowserMob.com and others can do multistep flows like logging in and > navigating to a page. > > StillAlive.com and the heroku add on is great for defining a full > cucumber-like test suite to ensure that not only is your site up, but it is > still functional. > > But I hope that people use some restraint when deciding which of their apps > they want to 'artificially keep awake', and find a nice balance that uses > resources wisely. > > Using the free plan on cloudflare.com CDN might be useful, particularly if > your main pages and most of the assets can be cached. (the page will load > quickly in the browser, from the cdn, then fire an uncacheable request to > wake up the server, without the user feeling like its slow). > > Actually using cloudflare is a win-win even after you're off the free > heroku plan, because it allows you to handle more concurrent users and load > things faster. > > > > > On Tue, Feb 14, 2012 at 11:34 AM, Nick <ntaberna...@gmail.com> wrote: > > > I've written a short blog post on how to keep your heroku dyno from > > 'timing out' which can lead to a slow loading site for those with a > > low amount of traffic. > > > > For those interested: > > > > http://beouk.blogspot.com/ > > > > -- > > You received this message because you are subscribed to the Google Groups > > "Heroku" group. > > To post to this group, send email to heroku@googlegroups.com. > > To unsubscribe from this group, send email to > > heroku+unsubscr...@googlegroups.com. > > For more options, visit this group at > > http://groups.google.com/group/heroku?hl=en. > > > > > > > -- > Thanks, > -John > > -- > You received this message because you are subscribed to the Google Groups > "Heroku" group. > To post to this group, send email to heroku@googlegroups.com. > To unsubscribe from this group, send email to > heroku+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en. >
-- Jason Dixon DixonGroup Consulting http://www.dixongroup.net/ -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.