Hey guys, I'll clarify a few things below:
Korny Sietsma wrote: > Hi folks - I've just deployed my first ever app to Heroku, and I'm wondering > if anyone could clarify exactly what you get for free? First, probably worth taking a quick look at what a dyno is: http://devcenter.heroku.com/articles/dynos As of this week, you now get 750 dyno hours for free. That's 750 hours to run whatever process you like. Given each month has between 672 and 744 hours (depending on the number of days in the month) it will allow you to run one process for free for a whole month with a few hours spare for something else. So that could be your web process (i.e., thin or unicorn for a ruby app) with an occasional worker or cron job. Alternatively in development it means you could run multiple web dynos and a couple of worker processes for a week without incurring any cost (so long as it cumulatively stays within 750 hours for the month). Chris Berkhout wrote: > Yeah, one dyno, no workers. > The pricing page shows you get 5MB in a shared database for free and I > think you're also limited to your app slug being 5MB. > I'm sure this was all clearer in previous versions of the web page. Not any more, workers are included in the 750 hour allocation now. Korny Sietsma wrote: > Hmm - it seems I might have a single worker - my 'accounts' page shows I've > incurred 5c in costs so far. > > Maybe this is a limitation of running clojure (which needs a JVM process) - > not sure, the clojure support doesn't seem to be documented anywhere :) What clojure support? ;) I think a change to the accounts page to make it clearer that you get the first 750 hours free for the month is coming shortly. Dmytrii Nagirniak wrote: > For me the biggest "limitation" on Heroku was that the "dyno" dies off > pretty quickly (~10-20 mins) if there are no requests. Then the app should > waste time warming up (read - loading Rails) again and again. > > Should not be a big deal for "demo" sites and ones with a consistent traffic > though. > > Heroku is great for showing stuff off. But expensive for non-free stuff. > > Additionally, as far as I know, you can't run any post-deploy things, > like precompiling assets, setting up cron jobs (there's add-on - once a day > free, hourly - paid) etc. Dyno idling only occurs when your app hasn't received any requests for a certain period, and when you are running just a single dyno. If you're running 2 or more dynos neither will idle and you wont have the first request latency of waiting for the app to restart. So you're right, if your site is getting consistent traffic it won't occur. (As an aside, the newer logging also gives good insight into when your app was idled, when it was restarted, how long it took, etc.) Trying to ignore the bias inherent in the fact that I now work for them, I was a long time fan but rarely a paying customer despite the number of sites I ran on the platform. I was skeptical of how much 1 dyno really gave you, and once I'd have to start paying for that *and* workers I always justified running it on my own VPS (and later my own co-located hardware). In reality 1 dyno was more capable than I gave it credit for (here's some basic benchmarks someone else did on the new stack http://michaelvanrooijen.com/articles/2011/06/01-more-concurrency-on-a-single-heroku-dyno-with-the-new-celadon-cedar-stack/), and it also bought me a managed platform with fault-tolerance, backup, and general sysadmin tasks taken care of. When I think back now at the amount of time I spent managing Chef, playing sysadmin, chasing co-lo providers about network outages, multiply it by my hourly rate and add +£80/month for rack space and power it probably would have been cheaper for me to keep things on Heroku. As for precompiling assets, what are you trying to do exactly? As far as SASS and similar are concerned, there are a couple of gems that take care of it. For Rails 3.1 I think it is handled automatically when your app slug is compiled. I've not been that impacted because I generally generate them locally to ensure it's all worked as expected and I'm not about to deploy a broken stylesheet, then commit and deploy *queue screams about committing generated code*. Abhinav Keswani wrote: > The pricing page has become somewhat gimmicky with the 750 hours free > thing. Just a flaky response to EY 500 hours free promo I think. > There's nothing new about this - you get a free dyno every month as > others have indicated. The old model only allowed a single web process. I know when I was doing client work and trying to demo things that was a pain because you'd have to pull out the credit card and start paying for workers and cron straight away, even though the site is probably hit once a day at most. Now the 750 hours can be allocated however you wish; I could scale up the web and worker processes to demo the complete site to a client, scale the web process to do performance testing, test out cron, etc. all without having to pay. Hope that helps clear things up. Will try make it to the Melb meetup when I'm back home in a couple of months, Glenn -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" 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/rails-oceania?hl=en.
