I would like to +1 the idea to come up with a way to get an always responsive app on Heroku for a reasonable price.
The current free plan makes the site so unresponsive on the first request that it's really only good for testing and toy sites, the next level for $36/month and 2 permanent dynos is a big step away for many people. I think there is a sweet spot in between there, in which Heroku could reach an monetize a large market segment. Just my 2 cents. :) Kevin On Feb 17, 2012, at 10:27 AM, Daniel Huckstep <[email protected]> wrote: > I thought the Cedar dynos didn't turn off when idle. Can't remember where I > got that idea from though, so I'm probably entirely wrong. > > But there's also http://devcenter.heroku.com/articles/dyno-idling which > suggest that you could scale your web dynos to zero (on Cedar) and use a > different process name to run the webserver (I'm assuming this would work, > haven't tried it). This is because the other processes (non web) could be > used for other fun things, like running redis (there was an example in a > presentation that showed some TCP routing) which you don't want to turn off. > > Also, in your post you say 450 hours, which is incorrect. It's 750. > -- > 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/-/h5MWNmpn3JIJ. > 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. -- 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.
