I think having a single permanent (i.e. always instantly responding) dyno for $10-20/month would make sense for a lot of people. It definitely provides for a much better user experience than the current free plan, especially for low traffic scenarios.
It could work like this: free plan as before, for testing etc. Once in a low-traffic production environment, upgrade the free dyno to a permanent dyno for $10-20/month. Then later, buy a second dyno for $35/month. Kevin On Feb 17, 2012, at 4:48 AM, Neil Middleton <neil.middle...@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> 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. >> 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 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.
