- 新しい順
- 投票が多い順
- コメントが多い順
Hello! The t2.micro instance type has just 1 GB of ram https://aws.amazon.com/ec2/instance-types/t2/. Depending on your workload, it might not have enough resources for what you need.
Additionally, t2 offers "burstable" CPU performance. This means that by default, you get a baseline level of performance according to the size, and it bursts when needed until the CPU bucket credits expire. Then it will burst again when needed when the CPU bucket credits refill. For more information about the CPU burst model, please check https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/burstable-credits-baseline-concepts.html
In your example, your baseline performance is 10% per VCPU (as explained in the above link) and you have 1 VCPU. For more insights about your particular case, I recommend checking the CloudWatch Metrics listed here https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/viewing_metrics_with_cloudwatch.html . I would start by checking the CPUUtilization as well as the CPUCreditBalance metric. If the latter one is close to zero, it means the instance is requiring additional CPU more than the time the burst credit allows to. If this happens, I have a couple of suggestions:
- Increase the instance size, so you can have a larger baseline performance and amount of CPU credits.
- Turn on "unlimited mode", which means the instance will be allowed to burst 100% of the time. For more information about unlimited mode, please check https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/burstable-performance-instances-unlimited-mode.html
If you need more assistance, I encourage you to create a new support case and then an engineer will have access to see your instance metrics and provide additional suggestions.
関連するコンテンツ
- 質問済み 6年前
- AWS公式更新しました 2年前
If CPU credits are a factor then consider switching from a t2 to a t3 as by default t3 launch as unlimited.
RoB correct, although some customers prefer to have unlimited mode as disabled by default to prevent any unforeseen billing charges.