Containers-roadmap: [Fargate] [request]: Burstable CPU

[luhn]

Tell us about your request
Similar to how t1/t2/t3 instances work, you are allocated a portion of the CPU but can burst to 100%.

Which service(s) is this request for?
Fargate

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
I've migrated a few lower-traffic services that were running t2 instances. I didn't think about it at the time, but 25% of a CPU core 100% of the time is a lot different than 100% of a CPU core 25% of the time. For more CPU heavy endpoints my latency increased substantially and brought the service to a crawl.

Are you currently working around this issue?
Paying for a full CPU core :(

Additional context

Attachments

[effyteva]

Any ETA on this one? We'd be glad to switch to Fargate, but this pricing model makes a huge difference.

[Sytten]

I would also like to see this come true, it is the only thing preventing us from using fargate.

[raehalme]

This would allow our tasks to start faster. After the task is up and running it no longer requires the same amount of CPU as it takes to prepare the task for operation.

[bogdanbrindusan]

Start-up time of services took a hit after moving to Fargate. Would highly appreciate to have this feature available.

[effyteva]

+1 (again)

[mreferre]

This is something we are discussing internally but we don't have a timeline to share. The problem is properly framed and understood.

Thanks for the engagement.