-
Notifications
You must be signed in to change notification settings - Fork 24.9k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Increase the merge factor to 32 for time-based data. (#94134)
This is a follow-up to #92684. #92684 switched from `TieredMergePolicy` to `LogByteSizeMergePolicy` for time-based data, trying to retain similar numbers of segments in shards. This change goes further, and takes advantage of the fact that adjacent segment merging gives segments (mostly) non-overlapping time ranges, to reduce merging overhead without hurting the efficiency of range queries on the timestamp field. In general the trade-off of this change is that it yields: - Faster ingestion thanks to reduced merging overhead. - Similar performance for range queries on the timestamp field. - Very slightly degraded performance of term queries due to the increased number of segments. This should be hardly noticeable in most cases. - Possibly degraded performance of fuzzy, wildcard queries, as well as range queries on other fields than the timestamp field.
- Loading branch information
Showing
3 changed files
with
25 additions
and
19 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,5 @@ | ||
pr: 94134 | ||
summary: Increase the merge factor to 32 for time-based data | ||
area: Engine | ||
type: enhancement | ||
issues: [] |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters