| ▲ | otterley 9 hours ago | |
They said in the article that they were running up to 200 pods at a time. Doing some back of the envelope math, 200 pods at $300,000 year is about $0.17/hour, which is exactly what an EC2 c5.xlarge costs per hour (on demand). That has 4 vCPUs, so about 800 vCPUs during peak, with $0.0425/CPU-hour. I do have some questions like: * Did they estimate cost savings based on peak capacity, as though it were running 24x7x365? * Did they use auto scaling to keep costs low? * Were they wasting capacity by running a single-threaded app (Node-based) on multi-CPU hardware? (My guess is no, but anything is possible) | ||
| ▲ | ebb_earl_co 9 hours ago | parent [-] | |
This is a helpful breakdown, thanks, @otterley. It is, by orders of magnitude, larger than any deployment that I have been a part of in my work experience, as a 10-year data scientist/Python developer. | ||