Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Is this way too high? How can we improve this? enter image description here

share|improve this question

IOPS is a difficult metric to 'improve'; unless you are in control of the code that's hammering your disk and can optimize its disk access patterns, there's not much you can do with this. Many IOPS typically equates to heavy system usage for a database or web server - which isn't necessarily a bad problem to have. Is there a reason you want to bring this number down?

share|improve this answer

We had a very large database in their biggest RDS instance and just got hammered with large IO spikes.. We just moved off RDS to a EC2 instance and things got better.

share|improve this answer
interesting, can you share more details? – brauliobo Mar 3 at 20:45
I'm not sure if its the same as it was many years ago.. but it RDS use to be on EBS so large IO operations would be bad. Moving to local disk sped things up alot – Mike Mar 3 at 21:52

Could it be the slow query log or general log doing lots of writes? See here.

share|improve this answer
Whilst this may theoretically answer the question, it would be preferable to include the essential parts of the answer here, and provide the link for reference. – Mark Henderson Oct 24 '12 at 0:19

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

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