From 3cbb8018d5086355bd8310ad25b1f126ce9ab150 Mon Sep 17 00:00:00 2001
From: Martijn van Groningen <martijn.v.groningen@gmail.com>
Date: Thu, 4 Jul 2024 09:20:19 +0200
Subject: [PATCH] Add some information about the impact of index.codec setting.
 (#110413)

---
 docs/reference/index-modules.asciidoc | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/docs/reference/index-modules.asciidoc b/docs/reference/index-modules.asciidoc
index 4f15bb1c1d694..8ab287191aaf2 100644
--- a/docs/reference/index-modules.asciidoc
+++ b/docs/reference/index-modules.asciidoc
@@ -79,7 +79,9 @@ breaking change].
     compression ratio, at the expense of slower stored fields performance.
     If you are updating the compression type, the new one will be applied
     after segments are merged. Segment merging can be forced using
-    <<indices-forcemerge,force merge>>.
+    <<indices-forcemerge,force merge>>. Experiments with indexing log datasets
+    have shown that `best_compression` gives up to ~18% lower storage usage
+    compared to `default` while only minimally affecting indexing throughput (~2%).
 
 [[routing-partition-size]] `index.routing_partition_size`::