You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I needed to compare two snapshots and I ran a "diff -qr" between them.
Noticed that z_rd_int/0 is consuming only a limited set of available resources (just 40% of cpu and only 25..28 percent of disk performance).
I have come to this conclusion by looking at the number of I/O requests in queue and they are zero, which means the drives are not fully stressed.
Then I thought: ok, this means zfs cannot process more data because is busy processing what has read so it must be fully busy with 100%, but then looking at cpu, I see only a quarter occupied by system process, another third busy on I/O and a third part idle.
Seeing this, I enable "top"-style process reporting in nmon and see that z_rd_int/0 is only taking 40%.
Instead I expected either for disks to burn in flames at 100% busy and few more I/O in "Inflight" queue, or cpu to be used at maximum.
zfs is 0.6.3, kernel is 3.16-2-amd64 on debian wheezy. notice that "diff" is taking a mere 3.9% fraction of cpu and no other processes are significantly consuming resources at that moment.
note: this happens only on datasets with lz4 compression! z_rd_int takes only few cpu percents on datasets with default compression
I needed to compare two snapshots and I ran a "diff -qr" between them.
Noticed that z_rd_int/0 is consuming only a limited set of available resources (just 40% of cpu and only 25..28 percent of disk performance).
I have come to this conclusion by looking at the number of I/O requests in queue and they are zero, which means the drives are not fully stressed.
Then I thought: ok, this means zfs cannot process more data because is busy processing what has read so it must be fully busy with 100%, but then looking at cpu, I see only a quarter occupied by system process, another third busy on I/O and a third part idle.
Seeing this, I enable "top"-style process reporting in nmon and see that z_rd_int/0 is only taking 40%.
Instead I expected either for disks to burn in flames at 100% busy and few more I/O in "Inflight" queue, or cpu to be used at maximum.
zfs is 0.6.3, kernel is 3.16-2-amd64 on debian wheezy. notice that "diff" is taking a mere 3.9% fraction of cpu and no other processes are significantly consuming resources at that moment.
note: this happens only on datasets with lz4 compression! z_rd_int takes only few cpu percents on datasets with default compression
The text was updated successfully, but these errors were encountered: