Measuring Disk I/O Performance WIndows Server
I am trying to monitor some disk activity on a hyper v host machine. I see many articles that tell me the range is 1-15ms is healthy 15-25ms is warning and 26ms or more is bad.
So I set the counter as logical disk \ avg sec read and write.
So my question is what do you set the scale to. Microsoft defaults it to 1000 so I am guessing on the graph if I see 20 that is 20ms? There are so many scales you can set it to I want to make sure it is the right one. I have read a lot of people say the defaults are wrong.
Also is this the best scale to look at for disk activity? I am basing the above from a TechNet article. Would I monitor the system disk like C? or the actual disk like V that is reading off the SAN where the VMs live? Thanks!
So I set the counter as logical disk \ avg sec read and write.
So my question is what do you set the scale to. Microsoft defaults it to 1000 so I am guessing on the graph if I see 20 that is 20ms? There are so many scales you can set it to I want to make sure it is the right one. I have read a lot of people say the defaults are wrong.
Also is this the best scale to look at for disk activity? I am basing the above from a TechNet article. Would I monitor the system disk like C? or the actual disk like V that is reading off the SAN where the VMs live? Thanks!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
So robincm, what do you use Trinity for? Do they host your vms?
Tintri VMstore is a VM-aware "SSD and HDD" storage device. All writes go to SSD, and SSD is used to cache reads from HDD. It uses the SSD very efficiently such that you can expect >90% (usually >99%) of IO to be from SSD and at <1ms latency.
You can see performance stats for individual VMs, set QoS for individual VMs, or just leave it alone and forget you ever had any storage performance issues.
https://www.tintri.com/products/tintri-vmstore
You can see performance stats for individual VMs, set QoS for individual VMs, or just leave it alone and forget you ever had any storage performance issues.
https://www.tintri.com/products/tintri-vmstore
We deploy Scale-Out File Server (SOFS) clusters for our larger storage backend needs. Storage Spaces provides the needed disk access and arbitration, can utilize a SSD tier, or tiers, and is scalable and resilient.
Our setup here in the shop hit 377K IOPS on one all flash JBOD. We have a configuration that allows for 1M IOPS out of that JBOD setup. When configured in a resilient disk array we can move 300K IOPS easily.
Cost per GB can't be beat by any storage vendor today.
Our setup here in the shop hit 377K IOPS on one all flash JBOD. We have a configuration that allows for 1M IOPS out of that JBOD setup. When configured in a resilient disk array we can move 300K IOPS easily.
Cost per GB can't be beat by any storage vendor today.
We normally measure Disk Performance in two major ways
MegaBytes per Second - MB/s
&
IO's per second - IOPS
and then associated performance indicators of Response time and Queue length
A conventional Enterprise Spinning disk spindle will do 200MB/s or 200IOPS whereas the equivalent SSD device will do at least 500MB/s and 30K+ IOPS
MegaBytes per Second - MB/s
&
IO's per second - IOPS
and then associated performance indicators of Response time and Queue length
A conventional Enterprise Spinning disk spindle will do 200MB/s or 200IOPS whereas the equivalent SSD device will do at least 500MB/s and 30K+ IOPS
Here is a blog post that gets in-depth on disk latency: TechNet: Measuring Disk Latency with Windows Performance Monitor (Perfmon).