1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
t3.micro have Burst CPU credits and can handle server load well if the server is intermittently access, but it cannot handle consistent loads well. In your case, the suspicion is that the CPU credits run out quickly thus causing page loading issues. ref: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/burstable-credits-baseline-concepts.html
If you have considerable consistent traffic, look for other instance types like c5 instances which have stable CPU performance and this will ensure your server is able to handle more load.
répondu il y a 2 ans
Contenus pertinents
- demandé il y a un an
- demandé il y a 3 mois
- demandé il y a 7 mois
- demandé il y a un an
AWS OFFICIELA mis à jour il y a 7 mois- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 3 mois
Well, I still don't have any traffic because I'm at an early stage, testing things and etc. But it is weird because the graphs EBSWritesBytes and EBSWritesOps, EBSReadsOps either are having peak moments and I do not have any traffic. Do you know what it can be?
It would be hard to pinpoint by looking at the graphs, I suggest you use iotop in your linux (assuming linux) or task manager/resource monitor (in windows) to find our what application is eating your disk IO and thus causing cpu usage as well. It is a possibility that logging is writing to your disk constantly as well.
iotop - https://www.geeksforgeeks.org/iotop-command-in-linux-with-examples/ Windows resource monitor - https://www.ghacks.net/2017/12/28/a-detailed-windows-resource-monitor-guide/