diff options
author | chrisrd <[email protected]> | 2017-09-30 08:49:19 +1000 |
---|---|---|
committer | Tony Hutter <[email protected]> | 2017-10-16 10:57:54 -0700 |
commit | 25d232f40713604dec1f6f6ef68802ab58115af0 (patch) | |
tree | 7d231915f590b480136e7b64d5b30380078dbdef /zfs.release.in | |
parent | edd7c24623529095bce10cb7ff3a8c3800c0067c (diff) |
Scale the dbuf cache with arc_c
Commit d3c2ae1 introduced a dbuf cache with a default size of the
minimum of 100M or 1/32 maximum ARC size. (These figures may be adjusted
using dbuf_cache_max_bytes and dbuf_cache_max_shift.) The dbuf cache
is counted as metadata for the purposes of ARC size calculations.
On a 1GB box the ARC maximum size defaults to c_max 493M which gives a
dbuf cache default minimum size of 15.4M, and the ARC metadata defaults
to minimum 16M. I.e. the dbuf cache is an significant proportion of the
minimum metadata size. With other overheads involved this actually means
the ARC metadata doesn't get down to the minimum.
This patch dynamically scales the dbuf cache to the target ARC size
instead of statically scaling it to the maximum ARC size. (The scale is
still set by dbuf_cache_max_shift and the maximum size is still fixed by
dbuf_cache_max_bytes.) Using the target ARC size rather than the current
ARC size is done to help the ARC reach the target rather than simply
focusing on the current size.
Reviewed-by: Chunwei Chen <[email protected]>
Reviewed-by: Brian Behlendorf <[email protected]>
Reviewed-by: George Melikov <[email protected]>
Signed-off-by: Chris Dunlop <[email protected]>
Issue #6506
Closes #6561
Diffstat (limited to 'zfs.release.in')
0 files changed, 0 insertions, 0 deletions