[ECS] [request]: Faster Target tracking scaling policies scale out
<!-- Please keep this note for the community --> ### 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 <!-- Thank you for keeping this note for the community --> **Tell us about your request** Currently ECS will wait 15+ minutes (default Cloudwatch metrics) or 5-6 minutes (detailed Cloudwatch metrics) before triggering a scale out which is way too slow to prevent issues for end users. This should be made much much faster to handle increased load without negatively impacting users. One way would be to add "evaluation-periods" option to Target tracking scaling policies to configure how many evaluation periods to wait before triggering a scale out. Another more drastic and effective solution would be to let EC2 agents proactively push increased CPU alerts to ECS/Auto scaling (and not wait for CloudWatch). Ideally, there would be two "evaluation-periods" options one for scale out (= being fast is key) and another for scale in (= balance cost vs stability) **Which service(s) is this request for?** ECS **Tell us about the problem you're trying to so
Posted by jeroenhabets on Aug 16, 2023, 12:29 PM
Tags
Related issues
- >Beef is already too expensive for most people.
- I gave this a go a couple of years ago.
- I haven't seen any use cases around me, although I'm not that advanced user.
- [BUG] Pro Max 5x Quota Exhausted in 1.5 Hours Despite Moderate Usage
- > Unfortunately it doesn't offer free hosting for hobbyists.
- Still the same HID remapping project from last month (I was hoping to be done by now, but hardware is hard): https://github.co...
Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments
pricing (Software)
>Beef is already too expensive for most people.
I gave this a go a couple of years ago.
I haven't seen any use cases around me, although I'm not that advanced user.
[BUG] Pro Max 5x Quota Exhausted in 1.5 Hours Despite Moderate Usage
> Unfortunately it doesn't offer free hosting for hobbyists.
Still the same HID remapping project from last month (I was hoping to be done by now, but hardware is hard): https://github.co...
This criticism seems like a complete non-sequitur to me.
Bring back the GitHub Copilot in the CLI commands to not break workflows
[ECS] [request]: Faster Target tracking scaling policies scale out
<!-- Please keep this note for the community --> ### 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 <!-- Thank you for keeping this note for the community --> **Tell us about your request** Currently ECS will wait 15+ minutes (default Cloudwatch metrics) or 5-6 minutes (detailed Cloudwatch metrics) before triggering a scale out which is way too slow to prevent issues for end users. This should be made much much faster to handle increased load without negatively impacting users. One way would be to add "evaluation-periods" option to Target tracking scaling policies to configure how many evaluation periods to wait before triggering a scale out. Another more drastic and effective solution would be to let EC2 agents proactively push increased CPU alerts to ECS/Auto scaling (and not wait for CloudWatch). Ideally, there would be two "evaluation-periods" options one for scale out (= being fast is key) and another for scale in (= balance cost vs stability) **Which service(s) is this request for?** ECS **Tell us about the problem you're trying to so
Comments (0)
No comments yet. Start the discussion.