You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are making our own instance right-sizing/recommendation tool and it would be nice if we could filter burstable instances by a minimum percentage of baseline utilization.
The text was updated successfully, but these errors were encountered:
Would this baseline utilization be input as per-vcpu or shared across all vcpus for an instance type?
How would "unlimited" credits be used or would they not be considered (t3's have unlimited enabled by default)?
Credits would be an interesting attribute to track (that is not present in the DescribeInstanceTypes API) to show as well and could potentially be used in calculations related to baseline utilization.
How would "unlimited" credits be used or would they not be considered (t3's have unlimited enabled by default)?
Since it's a setting and can be turned off and on, it wouldn't matter.
Although I gave it more thought and realized that it would be more useful if the number of CPU credits would part of the output, then we can do our own calculations to find out which instance would be cheapest with their average utilisation and CPU credits.
We are making our own instance right-sizing/recommendation tool and it would be nice if we could filter burstable instances by a minimum percentage of baseline utilization.
The text was updated successfully, but these errors were encountered: