Last update on that page say 1h: http://devcenter.heroku.com/articles/dyno-idling
----Vz Le mercredi 22 février 2012 18:09:48 UTC, Mike a écrit : > > Did heroku turn down the time your app stays "awake" without any > requests? In the past it was in the 20 to 25 minute range, IIRC. > > Mike > > On Wednesday, February 22, 2012 at 10:04 AM, Kevin Goslar wrote: > > With that, you keep Heroku unnecessarily busy by having them start a dyno > 24 times every day, and your app still sleeps 55 min per hour. > > > On Wed, Feb 22, 2012 at 4:17 AM, Nick <ntaberna...@gmail.com> wrote: > > An option for a single site is http://www.pingdom.com/ > > They can 'ping' your site every hour thereby keeping it awake. It's > free for one site. > > On Feb 21, 8:38 am, Sejensen <sejen...@gmail.com> wrote: > > Hi Neil and others > > > > These recommandations for Rails apps looks very good, > > > > But in my case i use Scala and the netty server and spin-up time is > > not good at all. And I am not sure it can be tuned so much as the > > sinatra case when the platform is java. > > > > Do anyone have any suggestions for my combo? > > > > Kind regards > > Steffen > > > > On Feb 20, 11:15 pm, Neil Middleton <neil.middle...@gmail.com> wrote: > > > > > > > > > > > > > > > > > To be brutally honest, there is no hard and fast rule, but I have > found the following: > > > > > - Rails is really fast at slowing down, so ensure that your > dependencies and initialisers are at an absolute minimum. > > > > > - Keep things small and lightweight, break your application up into > lots of smaller applications. Sinatra, for instance, spins up almost > instantly on Heroku and can take you a fair distance in terms of simple > functionality > > > > > - Generally speaking, the newer the Rails version, the quicker the > spinup time, especially if you're not using ActiveRecord > > > > > - If you're feeling beta-y, try running on Ruby 1.9.3, this makes a > massive difference to Rails. > > > > > Other than this, I'm not really aware of any silver bullet, but I do > know that lots of smaller more focused applications spin up better than one > monolithic Rails app, which is why Unix is so good I guess. > > > > > -Neil > > > > > On Monday, 20 February 2012 at 21:56, Ed Jones wrote: > > > > Neil said: > > > > > I host loads of apps on 1 web dyno and just make sure that the > spin up time is short enough that it's not a problem. > > > > > > Neil and others, thanks. > > > > > > I just launched a new (beta) app, and the response time is just > > > > horrible. > > > > > > Could you pass a few tips on how to "make sure that the spin up time > > > > is short enough"? > > > > Thanks!!! > > > > > > ed > > > > > > On Feb 17, 7:48 am, Neil Middleton <neil.middle...@gmail.com ( > http://gmail.com)> wrote: > > > > > I'm confused here. > > > > > > > The 'starter' package is only ~$35/mo which isn't exactly > monumentally expensive. Are you suggesting something between that and free? > > > > > What you're suggesting sounds like your charged by the CPU cycle > rather than the hours? > > > > > > > To be brutally honest, I host loads of apps on 1 web dyno and just > make sure that the spin up time is short enough that it's not a problem. > If I ever need to run more than 1 web dyno it's generally because the > traffic levels require it, in which case $35 becomes less of a problem. > > > > > > > Personally, I think that having a single dyno, which can still > serve hundreds of thousands of requests a day /for free/ is a pretty good > deal. I'm happy to pay $35 to double it. > > > > > > > Neil > > > > > > > On Friday, 17 February 2012 at 12:44, Nick wrote: > > > > > > Peter, > > > > > > > > I take your points well. I don't mean to try and 'do one over' on > > > > > > Heroku. I appreciate the service you offer very much. My thinking > > > > > > behind it was that you would never exceed the 450 hours of dyno > time > > > > > > allocated to each app so there wouldn't be a problem and if you > did > > > > > > you would be charged anyway. > > > > > > > > Is there a paid for solution from Heroku to achieve the same > result? > > > > > > The cost jump between 1 free dyno and paying for a dyno is quite > large > > > > > > for small applications. So perhaps you could offer a $10 package > which > > > > > > essentialy works the same way? If i'm honest I don't feel I pay > Heroku > > > > > > enough but I have too many small apps (10 or so) to pay for each > one > > > > > > to have a dedicated dyno. > > > > > > > > ? > > > > > > On Feb 16, 8:39 pm, Peter van Hardenberg <p...@heroku.com ( > http://heroku.com)> wrote: > > > > > > > As a database guy at Heroku, I'm not one to speak > authoritatively on > > > > > > > this, so please take this as the personal thoughts of someone > and not > > > > > > > an official statement. > > > > > > > > > We idle apps in order to avoid having to charge for them. The > more > > > > > > > people who prevent this behaviour, the more expensive our > "free" apps > > > > > > > become to run, and the more likely we are to have to change our > > > > > > > policies about what we can offer in a free app. > > > > > > > > > While I admire the ingenuity in this post, I would suggest > that you > > > > > > > reduce the amount of time your application takes to boot, or > simply > > > > > > > accept that a few seconds of lag on the first request after a > period > > > > > > > of idleness is a reasonable trade-off for free web hosting. > > > > > > > > > Peter > > > > > > > > -- > > > > > > 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(mailto: > heroku@googlegroups.com). > > > > > > To unsubscribe from this group, send email to > heroku+unsubscr...@googlegroups.com (mailto: > heroku+unsubscr...@googlegroups.com). > > > > > > 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 heroku@googlegroups.com(mailto: > heroku@googlegroups.com). > > > > To unsubscribe from this group, send email to > heroku+unsubscr...@googlegroups.com (mailto: > heroku+unsubscr...@googlegroups.com). > > > > 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 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. > > > -- > 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. > > > -- You received this message because you are subscribed to the Google Groups "Heroku" group. To view this discussion on the web visit https://groups.google.com/d/msg/heroku/-/q6LW_IAc_6YJ. 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.
