aboutsummaryrefslogtreecommitdiffstats
path: root/module/zfs/dnode_sync.c
diff options
context:
space:
mode:
authorSerapheim Dimitropoulos <[email protected]>2019-01-25 16:38:27 -0800
committerBrian Behlendorf <[email protected]>2019-01-25 16:38:27 -0800
commitc853f382db731e15a87512f4ef1101d14d778a55 (patch)
tree8f0ba611f5c4031bb55e61fb87b695fa4db3ea38 /module/zfs/dnode_sync.c
parentdf72b8bebe0ebac0b20e0750984bad182cb6564a (diff)
Change target size of metaslabs from 256GB to 16GB
= Old behavior For vdev sizes 100GB to 50TB we keep ~200 metaslabs per vdev and the metaslab size grows from 512MB to 256GB. For vdev's bigger than that we start increasing the number of metaslabs until we hit the 128K limit. = New Behavior For vdev sizes 100GB to 3TB we keep ~200 metaslabs per vdev and the metaslab size grows from 512MB to 16GB. For vdev's bigger than that we start increasing the number of metaslabs until we hit the 128K limit. = Reasoning The old behavior makes metaslabs grow in size when the vdev range is between 3TB (ms_size 16GB) and 32PB (ms_size 256GB). Even though keeping the number of metaslabs is good in terms of potential number of I/Os per TXG, these bigger metaslabs take longer to be loaded and after they are loaded they can take up a lot of memory because of their range trees. This change tries to put a boundary in memory and loading time for the specific range of vdev sizes. Reviewed-by: Matt Ahrens <[email protected]> Reviewed-by: Brian Behlendorf <[email protected]> Reviewed-by: Don Brady <[email protected]> Signed-off-by: Serapheim Dimitropoulos <[email protected]> Closes #8324
Diffstat (limited to 'module/zfs/dnode_sync.c')
0 files changed, 0 insertions, 0 deletions