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
Expand fragmentation table to reflect larger possibile allocation sizes
When you are using large recordsizes in conjunction with raidz, with
incompressible data, you can pretty reliably be making 21 MB
allocations. Unfortunately, the fragmentation metric in ZFS considers any
metaslabs with 16 MB free chunks completely unfragmented, so you can have a
metaslab report 0% fragmented and be unable to satisfy an allocation. When
using the segment-based metaslab weight, this is inconvenient; when using the
space-based one, it can seriously degrade performance.
We expand the fragmentation table to extend up to 512MB, and redefine the
table size based on the actual table, rather than having a static define. We
also tweak the one variable that depends on fragmentation directly.
Sponsored-by: Klara, Inc.
Sponsored-by: Wasabi Technology, Inc.
Signed-off-by: Paul Dagnelie <[email protected]>
0 commit comments