They changed the database pricing in January and I thought they
provided more specific details, but I guess they didn't:
http://blog.heroku.com/archives/2010/1/21/pricing_changes_part_i/
All my apps are running on blossom or koi db and I haven't had any
issues with speed unless I'm doing something stupid.
I agree about the inactivity, but think that has more to do with their
easy platform + good docs and support.
Welcome to easy hosting city.
On Oct 12, 6:38 am, mattsly <matt...@gmail.com> wrote:
> Thanks Chris - that's great to know that you're handling that much
> traffic w/ only 2 dynos and Koi. I have highly cachable content as
> well, and plan on aggressively using varnish, as well as caches_page
> behind that, and then rendering user specific partials ("welcome back
> username") w/ ajax (sounds like you're doing the same). I haven't
> turned all that on yet, b/c I want to really exercise the full end-to-
> end under some load first.
>
> With Koi, are your New Relic DB throughput and response time numbers
> pretty consistent? What is the variance that you're seeing in terms
> of database response time for the same queries? Any sign of timeouts
> caused by a slow DB response?
>
> And I wonder if anyone else out there has had success w/ Amazon RDS?
> The long-term pricing to get dedicated database is very attractive,
> and I'm more familiar w/ MySQL that PostGreSQL
>
> m
>
> p.s. As an aside, I am surprised by how little activity this group
> gets? Latest home page on heroku said there are 90,000+ apps running
> on the platform...but like 3 messages posted a day. Kinda weird?
> Implies that either a) people are just using the free "hello world"
> version, or b) it's just that damn easy that nobody is hitting
> issues :)
>
> On Oct 7, 11:39 pm, chris <mcclellan...@gmail.com> wrote:
>
>
>
> > It really depends a lot on how well you leverage caching. We run a
> > ~1.5mil page views / month site on heroku with just two (2!) dynos and
> > koi. But our pages are cached for ~3 hours via varnish, which heroku
> > provides for free. All users see (essentially) the same version of the
> > site, barring JS-driven login/logout links, and certain admin
> > functionality.
>
> > One thing you should keep in mind is that amazon RDS is mysql based
> > and heroku runs postgres DBs.
>
> > On Oct 7, 10:42 pm, mattsly <matt...@gmail.com> wrote:
>
> > > I really want to pull the trigger with Heroku. I love so much of it.
> > > I'm looking to move over a ~500K page views/month site that is
> > > decently data intensive, and still weighing my options wrt database,
> > > which may make or break my decision to use Heroku vs. EY, etc, given
> > > the price differences.
>
> > > Koi seems like a great deal. 20 GB is plenty for my app. My
> > > benchmarks so far seem promising. But "variable" performance has me
> > > concerned a bit...does anyone have more concrete numbers on just what
> > > that means? Anyone running decently high traffic sites on just Koi?
>
> > > The jump to Ronin is obviously dramatic in terms of price. Is there
> > > any more info on just what a "compute unit" is? Like RAM and I/O
> > > specs? It seems to me, given EC2 prices ("small ec2 is ~85/month
> > > variable, and large = ~910/year term < $100/month), that there should
> > > be a dedicated option for less than $200/month. Any hints of a Koi-
> > > like price drop in the near future here? My 2 cents to Heroku's
> > > pricing team would be treat the data layer as a break-even loss
> > > leader, and make up the revenue on the dyno/worker side...
>
> > > Amazon RDS seems like quite possibly the way to go. 3 year term for a
> > > small instance (1.7 GB) is $350 < 2 months of the cost of a Ronin
> > > instance! Has anyone gone this route and had success? Should I be
> > > worried about latency between Heroku and RDS? (it's all EC2, right?)
> > > Which zone should I have a DB placed in? (Virginia vs. California?)
>
> > > m
--
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.
