We saved 30% on Kubernetes using 70% more expensive VMs (opens in new tab)

(medium.com)

3 pointsrdsubhas1y ago6 comments

6 comments

3 comments · 1 top-level

motorest1y ago· 2 in thread

I guess this epiphany meant the company did some progress on how to deploy and run their Kubernetes clusters, but the blog post reads like "we were messing our deployment strategy really badly and causing us a whole lot of problems for no good reason". I mean, calling their setup "chaos monkey" sounds like a desperate attempt to whitewash the problems they were creating for themselves.

And what was the magic ingredient? Switching to committed use nodes that can give customers up to a 70% discount? Was this supposed to be surprising?

I mean, take any intro course on the fundamentals of any cloud provider. Cost management is always one of the first topics covered. The difference between spot instance and committed pricing is rendered quite obvious.

The cloud 101 recommendation was always committed instances to cover baseline, and spin up any other instance type, perhaps spot instances, to handle peaks.

Is this what they are celebrating? That someone at the company finally paid attention to a cloud 101 course?

rdsubhasOP1y ago

The article is about – saving 30% by switching from Spot to 70% more expensive VMs. It's the opposite of what you're talking about here.

> Switching to committed use nodes that can give customers up to a 70% discount?

This information is wrong. In which cloud do you see CUDs being 70% cheaper for standard machines?

Can you link any cloud provider's page that says – use "standard machines" for a higher discount than spot machines, it can be a productive conversation.

motorest1y ago

> The article is about – saving 30% by switching from Spot to 70% more expensive VMs. It's the opposite of what you're talking about here.

I don't think those values hold any meaning, specially after no concrete details are actually listed. For example, if hypothetical spot instances have a lower unit cost but your system needs to be over provisioned to account for systematic cold starts and cluster chatter, does it make any sense to say they are cheaper?

> This information is wrong.

Is it? Forward your complains to Google, then.

https://cloud.google.com/compute/docs/instances/committed-us...

1 more reply

j / k navigate · click thread line to collapse