I recently verified the IOPS in my RDS instances IOPS and I believe that it is too high. What is considered a good number/average for IOPS?

Are there any tools to check integrity and problems in a Mysql instance to help lower the IOPS, better than what is seen below?

enter image description here

closed as unclear what you're asking by Tom V, mustaccio, Max Vernon, joanolo, Marco Mar 22 '17 at 7:41

Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

  • 1
    A good IOPS is a zero IOPS. – mustaccio Mar 21 '17 at 19:26
  • Too high? This number is very small. 3 IOPS/GB of storage is high on a basic configuration, if the provisioned storage is >= 100 GiB. For smaller storage allocations, 300 IOPS is a standard value for reference. – Michael - sqlbot Mar 21 '17 at 23:31

A good number is rarely peaking to the available IOPS of the hardware or Cloud provider.

Your graph show rarely getting over 25. That is a very low number.

AWS carves up machines and sells you different amounts of CPU and IO. I can't say what your max is.

If you are hitting limits of CPU or IO with MySQL, then the first thing to do is to find the slowest query. It may need a better index, probably a 'composite' index. Or it may need to be reformulated in some simple way. Only after that, I would look at tuning. Then at hardware or AWS plan.

Not the answer you're looking for? Browse other questions tagged or ask your own question.