From 135c0356021e4c35e334f1bae8fc3193b608cd7e Mon Sep 17 00:00:00 2001 From: myoungwon oh Date: Fri, 23 May 2025 13:52:14 +0000 Subject: [PATCH] crimson/os/seastore: increase OI_MAX_LENGTH to avoid storing OI data in the omap tree Due to a recent change (adding shard_versions in object_info_t), the size of OI has increased to 236. This causes to store OI data to the omap tree because the size is over than OI_MAX_LENGTH. As a result, this results in performance drop in small random write. Signed-off-by: Myoungwon Oh --- src/crimson/os/seastore/onode.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/crimson/os/seastore/onode.h b/src/crimson/os/seastore/onode.h index 5d507460ded..71326c89167 100644 --- a/src/crimson/os/seastore/onode.h +++ b/src/crimson/os/seastore/onode.h @@ -16,7 +16,7 @@ namespace crimson::os::seastore { struct onode_layout_t { // The expected decode size of object_info_t without oid. - static constexpr int MAX_OI_LENGTH = 232; + static constexpr int MAX_OI_LENGTH = 236; // We might want to move the ss field out of onode_layout_t. // The reason is that ss_attr may grow to relative large, as // its clone_overlap may grow to a large size, if applications -- 2.39.5