Hello Deepak, A single / free dyno spins down when it is not in use. Much like passenger / mod_rails on your local box.
It cost ram/cpu/money to run a dyno on an ec2 instance. If you are not using it (and you are not paying for it), then there is no reason why Heroku should dish out the money to pay for something you are not using. If you want to pay for it by getting another dyno, then I guess you can be the judge on whether to have the app running or not. It seems curious to me that people want Heroku to pay for their staging environment to be up all the time. For me, staging is a pre-release testing environment. Guess others have a different view. Keenan On Aug 29, 2010, at 6:48 AM, deepak wrote: > what is the reasoning behind this. Did you test this or is it given in > the docs? > Deepak > > On Aug 26, 11:32 pm, Eric Anderson <e...@pixelwareinc.com> wrote: >> On 08/26/2010 11:30 AM, marcel wrote: >> ...... >> OTOH if you pay for at least 2 dynos then they NEVER spin down meaning >> your app is always nice and responsive even if nobody has it it for a while. >> ..... >> Eric > > -- > You received this message because you are subscribed to the Google Groups > "Heroku" group. > To post to this group, send email to her...@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 her...@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.
