2 Answers
- Newest
- Most votes
- Most comments
0
Hello.
What type of EBS are you using?
If you are using gp2 and there are a lot of writes, it may be possible that the burst credits are used up and the performance drops to the baseline throughput.
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/general-purpose.html#EBSVolumeTypes_gp2
https://repost.aws/knowledge-center/ebs-volume-burst-balance-low
0
I’ve seen similar things happen to Linux Machines but when the OS memory runs out.
You’d want to check all your system logs too as it could be file descriptors, memory issues etc.
You could if not already install the cloud watch agent and grab the extra metrics and logs for investigation purposes.
Relevant content
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 6 days ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated a year ago
Thanks! I’m using gp3 with 10.000 IOPS. Could the problem be too many writes to SQLite and log files? Which EBS configuration do you think I should use?
It's hard to tell without looking at actual metrics, application logs, etc. Have you checked the application logs and EBS CloudWatch metrics? https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using_cloudwatch_ebs.html