Determine IOPS

My boss asked that I determine the current IOPS on a server and recommend alternative solution.

He doesn't need specific metrics just a general idea of current iops and what new server should be able to handle the current needs.

From what I am reading I keep getting these extremely detailed breakdowns of number. I have used perfmon to collect the metrics per a website which  I thought could give me this information. I am now staring at the numbers but have no idea what to do with them. I assumed there was a general formula I could use based on my collections but I don't know what to do. Any suggestions would be help. Please see attached file of what I have and if anything else if need. Again I just need a general idea of the IOPS as this is not a mission critical server. Basic understandable explanation would be great. Thanks.
Perfmon.jpg
Tim OBrienSystems EngineerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Calvin PaxsonPremier Services Technical Support ManagerCommented:
From a cursory glance it looks like you are using 57 IOPS.  From wikipedia:

7,200 rpm SATA drives      HDD      ~75-100 IOPS[2]      SATA 3 Gbit/s      
10,000 rpm SATA drives      HDD      ~125-150 IOPS[2]      SATA 3 Gbit/s      
10,000 rpm SAS drives      HDD      ~140 IOPS[2]      SAS      
15,000 rpm SAS drives      HDD      ~175-210 IOPS[2]      SAS      

Realistically you want to get an average over time:

http://blog.synology.com/blog/?p=2086 

and then use the above chart to determine how many disks you need at max.  There is a penalty for IOPS when you are using RAID.
0
Tim OBrienSystems EngineerAuthor Commented:
Could you let me know which metrics you referred to when determining that number? I am fairly certain the metrics I provided were an average over 1 day which would be enough time to get good numbers.

Reading the documentation of what configuration I may need for the new server was more understandable. My main issue was filtering thru the values I provided and determining current IOPS. Thanks for your initial help!
0
Calvin PaxsonPremier Services Technical Support ManagerCommented:
DiskWrites/sec
DiskReads/sec
DiskTransfers/sec

Those should be the values you are interested in.  My math was bad but i'm sure you've already corrected it!
0
Introducing the "443 Security Simplified" Podcast

This new podcast puts you inside the minds of leading white-hat hackers and security researchers. Hosts Marc Laliberte and Corey Nachreiner turn complex security concepts into easily understood and actionable insights on the latest cyber security headlines and trends.

Tim OBrienSystems EngineerAuthor Commented:
I don't expect you to do all the work. I will review those numbers and hopefully figure it out. Thanks so much!

I will review the numbers and mark it as a solution shortly, don't know if it closes out question  if I mark as solution now so will hold off.
0
Tim OBrienSystems EngineerAuthor Commented:
Ok I added up the numbers and came to about 105 IOPS
DiskReads/sec - 4.6
DiskTrasnfers/sec  - 57.6
DiskWrites/sec - 53

105 IOPS is the limit this server can handle, from what I understand this doesn't indicate what the the new server should be planned for as this 105 IOPS is again the current limit of the server.

I read that referring to the Current Disk Queue Length will provide an indication to how much IOPS I should plan for so somehow the Total IOPS of 105 and the Current Disk Queue Length Metric of 8.9 will indicate how many IOPS I should plan for but I don't understand how the Current Disk Queue Length should be applied when forecasting.
0
Calvin PaxsonPremier Services Technical Support ManagerCommented:
Current disk queue length should be 2 plus 1 for each additional spindle in the machine.  If this machine has only one spindle then it is definitely over worked.  As for forcasting what is the workload?  SQL?  Exchange?  Other?  The application vendor should provide some sizing guidelines so that an informed decision can be made.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Tim OBrienSystems EngineerAuthor Commented:
Thanks for your feedback.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Server Hardware

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.