Try it now and let us know what you think. Switch to the new look >>
You can return to the original look by selecting English in the language selector above.
Standard Mode for Burstable Performance Instances
A burstable performance instance configured as standard is suited to workloads
with an average CPU utilization that is consistently below the baseline performance
of the instance.
To burst above the baseline, the instance spends credits that it has accrued in its
CPU credit balance.
If the instance is running low on accrued credits, performance is gradually lowered
to the baseline
performance level, so that the instance does not experience a sharp performance drop-off
when its accrued CPU credit balance is depleted. For more information, see CPU Credits and Baseline Performance for
Burstable Performance Instances.
Standard Mode Concepts
The standard mode is a configuration option for burstable
performance instances. It can be enabled or disabled at any time for a running or
stopped instance.
Note
T3 and T3a instances are launched as
unlimited by default. T2 instances are launched as
standard by default.
How Standard Burstable Performance Instances Work
When a burstable performance instance configured as standard is in a
running state, it continuously earns (at a millisecond-level resolution) a set rate
of earned credits per hour. For T2 Standard, when the instance is stopped, it loses
all its accrued credits, and its credit balance is reset to zero. When it is
restarted, it receives a new set of launch credits, and begins to accrue earned
credits. For T3 and T3a Standard, the CPU credit
balance persists for seven days after the instance stops and the credits are lost
thereafter. If you start the instance within seven days, no credits are lost.
A T2 Standard instance receives two types of CPU credits: earned credits and launch credits. When a T2 Standard instance is in a running state, it continuously earns (at a millisecond-level resolution) a set rate of earned credits per hour. At start, it has not yet earned credits for a good startup experience; therefore, to provide a good startup experience, it receives launch credits at start, which it spends first while it accrues earned credits.
T3 and T3a Standard instances do not receive launch credits.
Launch Credits
T2 Standard instances get 30 launch credits per vCPU at launch or start. For
example, a t2.micro instance has one vCPU and gets 30 launch credits,
while a t2.xlarge instance has four vCPUs and gets 120 launch credits.
Launch credits are designed to provide a good startup experience to allow instances
to burst immediately after launch before they have accrued earned credits.
Launch credits are spent first, before earned credits. Unspent launch credits are
accrued in the CPU credit balance, but do not count towards the CPU credit balance
limit. For example, a t2.micro instance has a CPU credit balance limit
of 144 earned credits. If it is launched and remains idle for 24 hours, its CPU
credit balance reaches 174 (30 launch credits + 144 earned credits), which is over
the limit. However, after the instance spends the 30 launch credits, the credit
balance cannot exceed 144. For more information about the CPU credit balance limit
for each instance size, see the credit table.
The following table lists the initial CPU credit allocation received at launch or start, and the number of vCPUs.
|
Instance type |
Launch credits |
vCPUs |
|---|---|---|
|
|
15 |
1 |
|
|
30 |
1 |
|
|
30 |
1 |
|
|
30 |
1 |
|
|
60 |
2 |
|
|
60 |
2 |
|
|
120 |
4 |
|
|
240 |
8 |
Launch Credit Limits
There is a limit to the number of times T2 Standard instances can receive launch credits. The default limit is 100 launches or starts of all T2 Standard instances combined per account, per Region, per rolling 24-hour period. For example, the limit is reached when one instance is stopped and started 100 times within a 24-hour period, or when 100 instances are launched within a 24-hour period, or other combinations that equate to 100 starts. New accounts may have a lower limit, which increases over time based on your usage.
Tip
To ensure that your workloads always get the performance they need, switch to Unlimited Mode for Burstable Performance Instances or consider using a larger instance size.
Differences Between Launch Credits and Earned Credits
The following table lists the differences between launch credits and earned credits.
|
Launch credits |
Earned credits |
|
|---|---|---|
|
Credit earn rate |
T2 Standard instances get 30 launch credits per vCPU at launch or start. If a T2 instance is switched from |
Each T2 instance continuously earns (at a millisecond-level resolution) a set rate of CPU credits per hour, depending on the instance size. For more information about the number of CPU credits earned per instance size, see the credit table. |
|
Credit earn limit |
The limit for receiving launch credits is 100 launches or starts of all T2 Standard instances combined per account, per Region, per rolling 24-hour period. New accounts may have a lower limit, which increases over time based on your usage. |
A T2 instance cannot accrue more credits than the CPU credit balance limit. If the CPU credit balance has reached its limit, any credits that are earned after the limit is reached are discarded. Launch credits do not count towards the limit. For more information about the CPU credit balance limit for each T2 instance size, see the credit table. |
|
Credit use |
Launch credits are spent first, before earned credits. |
Earned credits are spent only after all launch credits are spent. |
|
Credit expiration |
When a T2 Standard instance is running, launch credits do not expire. When a T2 Standard instance stops or is switched to T2 Unlimited, all launch credits are lost. |
When a T2 instance is running, earned credits that have accrued do not expire. When the T2 instance stops, all accrued earned credits are lost. |
The number of accrued launch credits and accrued earned credits is tracked by the
CloudWatch metric CPUCreditBalance. For more information, see
CPUCreditBalance in the CloudWatch metrics
table.
