#User write IOPS Size in kB
1 messages · Page 1 of 1 (latest)
hi @prime lynx what version of Harvest are you using. That screenshot looks like it's from an earlier version of Harvest. Checking that we didn't fix this
using aggr_disk_max_user_write_chain as an example, that counter is Average number of blocks transferred in each user write operation the *4 means we're using a 4KB block size and calculating the block size instead of number of blocks
yes, agreed. Was focusing on right and explaining how that value is calculated and why it is showing kilobytes. We'll fix the read iop size to match
Maybe overthink IOP as Name?
It was a lil irritating 😄
we're always open to improving naming - any suggestions? In this case, these panels were copied from 1.6 and without a good reason to change them, the original names were used.
I am not good at the naming game 😅