Tuesday, August 6, 2013

Re: Pricing model seems off for CMS usage

Cloud sql bills per hour, not per day, starting at $0.025 per hour (see https://developers.google.com/cloud-sql/docs/billing#per_use)

If your site caches and doesn't hit the database, it won't spin up the database. And after 15 minutes of non-use, it'll spin down (https://developers.google.com/cloud-sql/faq#how_usage_calculated)

Rob



On Tue, Aug 6, 2013 at 2:36 PM, Gary Mort <garyamort@gmail.com> wrote:
Looking at Cloud SQL the pricing model seems off for such usage.

Assume an app such as Wordpress, Drupal, Joomla, etc deployed to Google App Engine for PHP.  
Assuming it is a small website which will have sporadic traffic, it will cost: .36/day  or 10$/month just to host the mostly dormant mysql database.

This is about the same cost as a low end virtual host, which will still be faster.

It seems to me there should be some option for hibernating an SQL instance and then re-enabling it - that way a mostly dormant site could leave the engine hibernating at the cost of a delay for the first visitor.

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/b62f1a94-12e0-4117-a0f7-5f1533af8f1b%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/CA%2BbE6i00zj-P21MA%3DuhYQKRxut%3DUufUrcpc6dVqtxnpMCPQcNA%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

No comments:

Post a Comment