aws / aws/containers-roadmap

[Fargate] [request]: Burstable CPU

Open
#2,732 0 comments 61 reactions 1 assignee Claimed by @AbhishekNautiyal View on GitHub
Fargate Proposed
Dominant language
Shell
Stars
5.4k
Forks
334
PR merge metrics
No merged PRs in 30d

Description

### Community Note

* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment

**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**
This was originally requested [here](https://github.com/aws/containers-roadmap/issues/163), but an entirely different thing was delivered and the request closed asking for a new request to be opened for the original request!

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.