Closed KJ7LNW closed 10 months ago
In case it matters, the sda
sector size is 4k, not 512:
# blockdev --getss /dev/sda
4096
# blockdev --getss /dev/nvme0n1
512
# blockdev --getss /dev/nvme1n1
512
dool
defaults to show disk and network in bits per second. Try --bytes
to get output in bytes if that's what you'd prefer.
Ahh! Ok, that explains it.
Bits-per-second makes sense for network, but that is unusual for a storage, and it deviates from both Dag's original dstat and RH's dstat replacement for disk IO stats.
What do you think about defaulting everything to bytes/sec except network?
I use dool
to watch my network interfaces which then results in disk read/write. If they were in different scales it would mess me up. I'm going to leave things as they are. Feel free to use --bytes
if it works better in your environment.
Got it, thanks for the hint. I only mentioned changing the default to bytes because the README.md says "Dool is a Python3 compatible fork of Dstat."
IIRC, the original dstat uses bytes by default. Now that I know about --bytes
, I'm fine either way, just not sure how strict you had planned to be in terms of dstat compatibility.
Thanks for your help!
This comes up every so often, I should put a section in the README
SUMMARY
Dool shows high MB/s rates for disks, but
dstat
andiostat
agreeISSUE TYPE
DOOL VERSION
DSTAT VERSION (PCP version for comparison, I know this one is not dool):
OS / ENVIRONMENT
Oracle Linux 9
STEPS TO REPRODUCE
EXPECTED RESULTS
We expect what
iostat
anddstat
show:ACTUAL RESULTS
as above, but also mixed into the output,
dool
shows 48M/s iinstead of ~5M/s:Here is a longer run. Note that
iostat
anddstat
numbers agree, butdool
's numbers are much bigger than they should be: