summaryrefslogtreecommitdiffstats
path: root/module/icp/asm-x86_64
diff options
context:
space:
mode:
authorMatthew Ahrens <[email protected]>2019-06-12 13:06:55 -0700
committerBrian Behlendorf <[email protected]>2019-06-12 13:06:55 -0700
commitd9cd66e45f285356624d26eb92e10e2baf2738ee (patch)
tree186ed8e9a22f28bf9a6f56b83e66f4371abc141a /module/icp/asm-x86_64
parent10269e02f9d0feef815a83d718728b51a9633d16 (diff)
Target ARC size can get reduced to arc_c_min
Sometimes the target ARC size is reduced to arc_c_min, which impacts performance. We've seen this happen as part of the random_reads performance regression test, where the ARC size is reduced before the reads test starts which impacts how long it takes for system to reach good IOPS performance. We call arc_reduce_target_size when arc_reap_cb_check() returns TRUE, and arc_available_memory() is less than arc_c>>arc_shrink_shift. However, arc_available_memory() could easily be low, even when arc_c is low, because we can have tons of unused bufs in the abd kmem cache. This would be especially true just after the DMU requests a bunch of stuff be evicted from the ARC (e.g. due to "zpool export"). To fix this, the ARC should reduce arc_c by the requested amount, not all the way down to arc_size (or arc_c_min), which can be very small. Reviewed-by: Tim Chase <[email protected]> Reviewed by: Brian Behlendorf <[email protected]> Reviewed-by: George Melikov <[email protected]> Signed-off-by: Matthew Ahrens <[email protected]> External-issue: DLPX-59431 Closes #8864
Diffstat (limited to 'module/icp/asm-x86_64')
0 files changed, 0 insertions, 0 deletions