News for hackers. Stuff that matters.

A comment on We use Kubernetes and spot instances to reduce EC2 billing up to 80%. Parent comment

Re:We use Kubernetes and spot instances to reduce EC2 billin... by rumanator on Tuesday February 25, 2020 @06:11AM (#22412289)
The main problem with AWS Fargate, as with most of AWS's offering, is cost. More precisely, granularity. AWS Fargate cost infrastructure, at best, charges you per ceiling of 0.25 vCPU and 0.5GB of RAM (rounded up) per second, with a ceiling of 2GB of RAM. If your containers have some spiky workloads that require more than 2GB of RAM then the coarseness goes up and your are charged per 1GB of RAM (rounded up) per second. That means a spiky workload can lead you to spend more than a month's worth of a EC2 instance with 2GB of RAM (say, T3.small with 2vCPU and 2GB of RAM).

The whole service becomes even more ridiculous if a company is already operating EC2 instances or even kubernetes clusters on EC2 spot instances (the topic of this discussion), because more often than not these workloads can be already covered by the cluster's unused capacity.

[ Parent | on HN ]
Re:We use Kubernetes and spot instances to reduce EC2 billin... by maniktan on Monday March 02, 2020 @05:57PM (#22469991)
Product@SpotInst here. Just fyi, we have customers launch Spark workloads that require 300G RAM and we are able to efficiently deliver this capacity by ensuring that the underlying infrastructure is shared with other pods that are not memory bound. We bin-pack, scale up and down quickly, while allowing you to have warmed-up spare capacity when needed to ensure that your pods/tasks are serviceable immediately.
[ Parent | on HN ]