copilot-cli icon indicating copy to clipboard operation
copilot-cli copied to clipboard

CPUUtilization Service metrics

Open musenaw opened this issue 2 years ago • 1 comments

Hi!

We are using AWS Copilot in our producction environments to some percentage of users, and in order to sent more traffic to this new architecture we want to be sure to have the right shape of minimin tasks running.

We have some spikes of 127% of maximum CPUUtilization and average is on 35%, reading ECS documentation about it link to doc and example says the following

In this example, the CPU utilization will only go above 100% when the CPU units are defined at the container level.  
If you define CPU units at the task level, the utilization will not go above the defined task-level limit.

As per my understanding cpu its defined at task level and not at cluster level, we have 8 tasks with 1 vcpu defined in our manifest and should never go up more than 100%. How we should interpret those max CPUUtilization spikes more than 100%?

Thanks!

musenaw avatar Feb 05 '24 08:02 musenaw

Hello @musenaw. I would be surprised to see the spike could be as high as 127% as well for cpu usage...since you are absolutely right we set the cpu at task level and it seems to be a hard limit. Most likely there is some nuance between what it is described in the doc vs how ECS actually calculates the metrics. However, it def. means the task is unhealthy and ECS scheduler will spin up more tasks if it gets more datapoint like this.

iamhopaul123 avatar Feb 05 '24 22:02 iamhopaul123

This issue is stale because it has been open 60 days with no response activity. Remove the stale label, add a comment, or this will be closed in 14 days.

github-actions[bot] avatar Apr 06 '24 00:04 github-actions[bot]

This issue is closed due to inactivity. Feel free to reopen the issue if you have any further questions!

github-actions[bot] avatar Apr 20 '24 00:04 github-actions[bot]