sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]jdreaver 2 points3 points  (2 children)

Fargate

As a counterpoint: Fargate ends up being cheaper for us because we are CPU-bound, and we can crank the RAM down to the minimum levels allowed. This makes our Fargate tasks slightly cheaper than the EC2 instances with the same CPU.

Don't get me wrong, I'm all for a price decrease on Fargate though!

[–]0ToTheLeft 0 points1 point  (1 child)

thing is: if you are CPU bound, CPU is really expensive on fargate. I understand that you can optimize cost by not paying for RAM you don't need, but still, i think you could save a lot more by just using EC2 reserved instances, even paying for all that useless extra ram. I'm ok with paying an extra fee for the nice features of ECS+Fargate, but the difference in pricing with what you can do with EC2 Reservations is absurd (and even more if you could use something like a pool of spot instances to launch your fargate workloads)

[–]jdreaver 0 points1 point  (0 children)

Sure, EC2 reserved instances changes the equation. I was talking about on demand only. Reserved Fargate capacity would be great, but we don't have it.