Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proposal: Change Disk Performance reporting #261

Open
stebet opened this issue May 31, 2017 · 0 comments
Open

Proposal: Change Disk Performance reporting #261

stebet opened this issue May 31, 2017 · 0 comments

Comments

@stebet
Copy link
Contributor

stebet commented May 31, 2017

Currently the the new disk/volume performance reporting is inconsistent between providers. For example for WMI it's pulling the number of bytes Read/Write whereas the Orion provider is giving the number of reads/writes.

The number of bytes being read/written to disk only tell half the story as that differs wildly between for example DB servers and web servers and is really dictated by the type of disks (NAS volume/HDD/SSD), and a pure throughput number doesn't actually tell you if it is affecting performance.

My proposal is that it be changed to rather report on the number of reads/writes, and also adding disk queue length and disk latency metrics as those give in my opinion a much clearer image of the performance impact disk/volume IO might be having on the server. These metrics are also properly reported in all providers.

Discuss! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant