2

enter image description hereenter image description hereenter image description hereI am a beginner in this AWS technology area. Every day I start and stop my RDS instance(db.t2.micro (MSSQL Server)) of AWS using a lambda expression. The fact that CPU credit balance acquired and spent on a daily basis and that CPU credit balance affect CPU usage described by AWS documentation. Daily CPU usage maximizes up 10% use. But for one day CPU credit balance was zero and CPU usage is high. I have no reason behind that's odd behaviour of rds instance. Can anyone describe me the reason? Please anyone can explain?

enter image description here

  • Sorry, but your question is unclear. Do you have a specific question? If you are asking why your CPU usage was high one day, then you have not supplied enough information for us to provide any advice. – John Rotenstein Dec 12 '19 at 08:47
  • thanks for the comment @John.i hope now the image will clarify my question. –  Dec 12 '19 at 10:00
  • @JohnRotenstein sir can you describe me now. I am worried about this issue. –  Dec 13 '19 at 08:53
  • If the database CPU usage was high (for whatever reason), it would have consumed the CPU Credits, resulting in no 'burst' capacity. However, there's no way to know why the CPU usage was high aside from observing running jobs on the database at the time. If this has a negative impact on your systems, then use a larger instance type or, preferably, a different instance family that provides consistent performance (but at a higher cost). – John Rotenstein Dec 13 '19 at 20:31
  • thanks for the comment. Can I update my credits after it fully used ?? –  Dec 19 '19 at 07:47
  • With t2 instances, once your credits are used up, you go into degraded mode (I think it's 10% of the CPU capacity). You can upgrade to t3 instances, which work in "unlimited" modes (i.e. you pay for additional CPU power that you use once you've spent your credits) – Sébastien Tromp Jun 21 '22 at 06:50

0 Answers0