4 ms·

also www.heroku.com

• nopal 16y ago
  I really wish they'd show me what I can run on Koi (links to current sites). I know they make deployment a snap, but I worry that I'd be forced to add more and more resources to keep my site running as I'd hope.
  • bricestacey 16y ago
    The only difference between Blossom and Koi is the size of the database. The only way to improve performance is to increase the number of dynos or workers you use.
    • zrail 16y ago
      This is actually possible to do dynamically[1] so you can keep your costs down. I found this post last week and implemented it over the weekend, and it's pretty neat to watch it work. So far I've only implemented this for workers, but it's certainly possible[2] to implement it for dynos. [1]: http://blog.darkhax.com/2010/07/30/auto-scale-your-resque-workers-on-heroku http://blog.darkhax.com/2010/07/30/auto-scale-your-resque-wo... [2]: http://github.com/ddollar/heroku-autoscale http://github.com/ddollar/heroku-autoscale
• Timothee 16y ago
  Interesting, I didn't know they had a free plan. (never looked into it that much) 5MB of DB and 1 "dyno" would be plenty for what I have in mind (let's be honest: 1kB would be sufficient :)), so I'll definitely keep it in mind as well. But now the eternal question for me comes back again: Ruby or Python... Thanks for pointing it out to me!