From: Sage Weil Date: Fri, 20 Jan 2017 18:59:56 +0000 (-0500) Subject: os/bluestore/BlueFS: increase size threshold before we flush (and generate io) X-Git-Tag: v12.0.0~99^2~1 X-Git-Url: http://git-server-git.apps.pok.os.sepia.ceph.com/?a=commitdiff_plain;h=c776710a8ec04a2fd810fc5a1899fa8868cbc80a;p=ceph.git os/bluestore/BlueFS: increase size threshold before we flush (and generate io) Having this too high means you might be more bursty. In practice, though, the commit path is doing explicit syncs on small chunks anyway. And compaction work should probably stay reasonably chunky. Signed-off-by: Sage Weil --- diff --git a/src/common/config_opts.h b/src/common/config_opts.h index fc54b3d3bc66..bef51fde53e3 100644 --- a/src/common/config_opts.h +++ b/src/common/config_opts.h @@ -988,7 +988,7 @@ OPTION(bluefs_min_log_runway, OPT_U64, 1048576) // alloc when we get this low OPTION(bluefs_max_log_runway, OPT_U64, 4194304) // alloc this much at a time OPTION(bluefs_log_compact_min_ratio, OPT_FLOAT, 5.0) // before we consider OPTION(bluefs_log_compact_min_size, OPT_U64, 16*1048576) // before we consider -OPTION(bluefs_min_flush_size, OPT_U64, 65536) // ignore flush until its this big +OPTION(bluefs_min_flush_size, OPT_U64, 524288) // ignore flush until its this big OPTION(bluefs_compact_log_sync, OPT_BOOL, false) // sync or async log compaction? OPTION(bluefs_buffered_io, OPT_BOOL, false) OPTION(bluefs_allocator, OPT_STR, "bitmap") // stupid | bitmap