Hacker News new | ask | show | jobs
by FLUX-YOU 3388 days 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.
2 comments
rvs-ie 3387 days 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.

link
ProblemFactory 3387 days 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.

link