-
Notifications
You must be signed in to change notification settings - Fork 25.5k
Remove zstd feature flag for index codec best compression. #112665
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from 13 commits
cd148ca
57ca3f4
9c185ed
ca2b029
69636e0
45c424a
f1488f0
7dd45f5
54975f5
bbaddbd
af45a23
d907f1b
6297da9
53a780a
58e4898
49adb6d
ea8dd1f
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -32,6 +32,7 @@ | |
"CRUD", | ||
"Client", | ||
"Cluster Coordination", | ||
"Codec", | ||
"Data streams", | ||
"DLM", | ||
"Discovery-Plugins", | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,13 @@ | ||
pr: 112665 | ||
summary: Remove zstd feature flag for index codec best compression | ||
area: Codec | ||
type: enhancement | ||
issues: [] | ||
highlight: | ||
title: Enable ZStandard compression for indices with index.codec set to best_compression | ||
body: |- | ||
Before DEFLATE compression was used to compress stored fields in indices with index.codec index setting set to | ||
best_compression, with this change ZStandard is used as compression algorithm to stored fields for indices with | ||
index.codec index setting set to best_compression. Experiments have shown that ZStandard offers lower storage usage | ||
(upto ~12%) and higher indexing throughput (upto 14%) compared to DEFLATE. | ||
notable: true |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -76,14 +76,16 @@ breaking change]. | |
|
||
The +default+ value compresses stored data with LZ4 | ||
compression, but this can be set to +best_compression+ | ||
which uses {wikipedia}/DEFLATE[DEFLATE] for a higher | ||
compression ratio, at the expense of slower stored fields performance. | ||
which uses {wikipedia}/Zstd[ZSTD] for a higher | ||
compression ratio, at the expense of slower stored fields read 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>>. Experiments with indexing log datasets | ||
have shown that `best_compression` gives up to ~18% lower storage usage in | ||
the most ideal scenario compared to `default` while only minimally affecting | ||
indexing throughput (~2%). | ||
have shown that `best_compression` gives up to ~28% lower storage usage and | ||
better indexing throughput (up to ~10%) in the most ideal scenario compared | ||
|
||
to `default` while affecting get by id latencies up to 10%. The higher get | ||
|
||
by id latencies is not a concern for many use cases like logging or metrics, since | ||
these don't really rely on get by id functionality (Get APIs or searching by _id). | ||
|
||
[[index-mode-setting]] `index.mode`:: | ||
+ | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we also update the note on higher indexing throughput here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, I reworded this to: 58e4898