Adding a single graph for a $2000/mo DB, only performing read only transactions at 30% of its connection limit doesn't sound like putting the DB through its paces, and not real world.
115 karma · joined January 21, 2014
Adding a single graph for a $2000/mo DB, only performing read only transactions at 30% of its connection limit doesn't sound like putting the DB through its paces, and not real world.
And even then, one still needs to factor in the 'other' costs like I/O or IOPs, disk (persistent/EBS), IPs, internet and inter-region data transfer… before you understand the real cost.
And then you need to compare to other instance types (which soon will cover the full alphabet -- c, cg, cr, g, h, i, m, r, t… ) and then other providers.
You still have several unresolved issue -
1. Are your assumption on usage (cpu, I/O, internet etc) correct? Will they change? 2. How do I compare performance across providers for a given VM specification. 3. Can I get support when I need it?
And I am sure there are others
It certainly means there is room for other players who just make it simple, whether they are infrastructure folk (like DO/Linode etc) or platform plays that make the pricing understandable by the audience they are trying to target (like Heroku/Ninefold)
Here's a recent interview with Matz from RubyConf13 (Miami Nov 2013) http://multifaceted.io/2013/rubyconf-13-a-chat-with-matz/ that may be of interest.
It's about making developers happy…
I am confident that with some refinements a good outcome will be reached.
Color coding comments to flag they as 'pending' is fine. But complete hiding them sounds too strong
Its great to have the conversation on how to improve HN comments