EC2 T-Instance CPU Credits Depleted: Sustained Baseline Throttling Before Resizing

Question

Symptom

When an Amazon EC2 T2, T3, or T4g instance shows CPUCreditBalance near zero during peak hours while CPUUtilization stays at the instance baseline, the goal is to determine whether the workload is being throttled to baseline CPU performance because credits are exhausted, and whether that pattern justifies resizing to a fixed-performance instance class or adjusting the workload instead.

Constraints: a single low credit sample is not conclusive because diurnal load patterns can temporarily drain credits. T3 Unlimited may bill for surplus CPU instead of throttling, masking the symptom as higher cost rather than reduced performance. Credit balances are instance-specific and do not transfer across stops or size changes.

Does a multi-day downward trend in CPUCreditBalance confirm sustained baseline throttling rather than intermittent bursting?
Should the instance be resized to a fixed-performance class, or should the workload be changed to stay within the T-instance baseline?
What difference does T3 Unlimited surplus-credit billing make compared with standard mode?

Tasadduq Burney · Answer

Direct ResolutionSustained baseline throttling is confirmed only in Standard credit mode when the multi-day CPUCreditBalance trend is near zero, not in Unlimited mode.If the demand consistently meets or exceeds the instance baseline, resizing to a fixed-performance class (M, C, R) is justified. If demand is spiky with sufficient idle periods for credit replenishment, workload optimization or increasing the T-instance size is preferred over immediate resizing.The single missing diagnostic detail required to confirm the correct path is the instance's credit specification: Standard or Unlimited.Explanation vs. Confirmed FactsLikely ExplanationA low credit balance alone is insufficient; diurnal load can temporarily drain credits. The distinction between Standard (throttling at zero balance) and Unlimited (billable surplus credits above baseline) is critical.Confirmed FactsCPU credits are instance-specific and do not transfer across stops or size changes.A multi-day downward trend towards zero confirms sustained demand exceeding baseline in Standard mode.In Unlimited mode, exceeding the baseline results in surplus charges, not performance throttling.Required StepsVerify the instance's credit specification (Standard or Unlimited) via EC2 details.Gather 7–14 days of CloudWatch data for CPUCreditBalance, CPUUtilization, and CPUSurplusCreditsCharged.If Standard mode and utilization is pinned at baseline with depleted credits, throttling is confirmed.If Unlimited mode, review CPUSurplusCreditsCharged against fixed-performance instance pricing.Decision CriteriaSteady demand at/above baseline $ightarrow$ Resize to fixed-performance.Spiky demand with credit recovery $ightarrow$ Optimize workload or increase T-instance size.

EC2 T-Instance CPU Credits Depleted: Sustained Baseline Throttling Before Resizing

1 answer

Direct Resolution

Sustained baseline throttling is confirmed only in Standard credit mode when the multi-day `CPUCreditBalance` trend is near zero, not in Unlimited mode.

Explanation vs. Confirmed Facts

Likely Explanation

Confirmed Facts

Required Steps

Decision Criteria

Your perspective belongs here.

1 question comment