4 ms·

The pricing is listed here: https://cloud.google.com/sql/docs/postgres/pricing#pg-pricing https://cloud.google.com/sql/docs/postgres/pricing#pg-pricin... Sampl

The pricing is listed here: https://cloud.google.com/sql/docs/postgres/pricing#pg-pricing https://cloud.google.com/sql/docs/postgres/pricing#pg-pricin... Sample monthly pricing: db-f1-micro instance : $7.56 for compute; 10GB HDD : $0.9 for storage; No network cost if the database instance is talking to a GCE VM in the same region; Disclaimer: I work on Google Cloud SQL

merb 10y ago
when ha would cost the same i.e. ~20€ than that would be amazingly cheap. i mean on aws you would pay the same (20 €), but you need to pay 1 year upfront.. and if ha would be like 16 € you would only be a little bit more expensive than a 3 year aws rds offering (1€ per month), which is less a problem since the storage is cheaper and you are way more flexible (canceling and recreating to a bigger instance)
FLUX-YOU 10y ago
>db-f1-micro >db-g1-small >db-n1-highmem-2 >db-n1-standard-8 >D32 Database Instance (16GB RAM) >Tier D0, D1, D2, D4, D8, D16, D32 What's up with cloud instance naming schemes? I get this is kind of similar to Amazon, but man, I bet these are really unwieldy in conversations esp. if someone is new to a platform.
- ProblemFactory 10y ago
  > What's up with cloud instance naming schemes? There's at least 2 performance dimensions for provisioning an instance: vCPUs and memory. Often also GPUs, local SSDs, local HDDs. And then you have multiple generations of hardware, which aren't 100% comparable to each other. So coming up with a "fully systematic" naming scheme is not really possible without listing all the parameters, and then you lose the benefit of having a name.
- rvs-ie 10y ago
  We know. That's why PostgreSQL pilots hopefully clearer pricing structure where you choose how much CPU and RAM is needed and pay per CPU and GiB of ram. No more `db-nX-<something>-X`. You'll still see instance size names for a while though. I think D0-D32 are for first generation of CloudSQL (which is MySQL only). db-* are for second generation and match GCE instance names.

merb 10y ago

when ha would cost the same i.e. ~20€ than that would be amazingly cheap. i mean on aws you would pay the same (20 €), but you need to pay 1 year upfront.. and if ha would be like 16 € you would only be a little bit more expensive than a 3 year aws rds offering (1€ per month), which is less a problem since the storage is cheaper and you are way more flexible (canceling and recreating to a bigger instance)

FLUX-YOU 10y ago

>db-f1-micro >db-g1-small >db-n1-highmem-2 >db-n1-standard-8 >D32 Database Instance (16GB RAM) >Tier D0, D1, D2, D4, D8, D16, D32 What's up with cloud instance naming schemes? I get this is kind of similar to Amazon, but man, I bet these are really unwieldy in conversations esp. if someone is new to a platform.

ProblemFactory 10y ago
> What's up with cloud instance naming schemes? There's at least 2 performance dimensions for provisioning an instance: vCPUs and memory. Often also GPUs, local SSDs, local HDDs. And then you have multiple generations of hardware, which aren't 100% comparable to each other. So coming up with a "fully systematic" naming scheme is not really possible without listing all the parameters, and then you lose the benefit of having a name.
rvs-ie 10y ago
We know. That's why PostgreSQL pilots hopefully clearer pricing structure where you choose how much CPU and RAM is needed and pay per CPU and GiB of ram. No more `db-nX-<something>-X`. You'll still see instance size names for a while though. I think D0-D32 are for first generation of CloudSQL (which is MySQL only). db-* are for second generation and match GCE instance names.