S2D Performance History database

Question

I've pulled some metrics data of a VM with PS get-clusterperformancehistory over a timeframe of 1 Day:
VHD.IOPS.Read, VHD.IOPS.Write, VHD.Latency.Average, VHD.Throughput.Read, VHD.Throughput.Write
While examining the throughput data, I faced unrealistic values in my calculations.
Looking deeper into the metrics, I found that counters VHD.Throughput.Read, VHD.Throughput.Write varies in the unit used when recording the data - sometimes it is MB/s, on other it is KB/s.

This makes it unnecessary tight if you want to do reporting over a certain timeframe.
At least I'd expect a parameter in the commandlet to keep the pulled data in one unit (i.e. MB/s)
Or is there any cheat to come around this?

Answer 1

Hi there,

I suppose we cannot determine the value which will be expressed in KB/s or in MB/s

Performance history is stored for up to one year, with diminishing granularity. For the most recent hour, measurements are available every ten seconds. Thereafter, they are intelligently merged (by averaging or summing, as appropriate) into less granular series that span more time. For the most recent day, measurements are available every five minutes; for the most recent week, every fifteen minutes; and so on.

---

--If the reply is helpful, please Upvote and Accept it as an answer--

Answer 2

Sorry - my bad.
Problem was not in pulled data, but a mismatch when importing into Excel (mismatch of decimal separators) caused by different language settings on server and workstation.