http_logs add force merge to 1 segment#90
Conversation
Measure the performance of sort operations after force merging to 1 segment. PR #48533 adds a new merge policy that interleaves old and new segments on force merge. We would like to check the sort performance with this policy after docs are merged to 1 segment.
danielmitterdorfer
left a comment
There was a problem hiding this comment.
Thanks! I left a comment on the force-merge timeout.
http_logs/challenges/default.json
Outdated
| "name": "force-merge-1-seg", | ||
| "operation": { | ||
| "operation-type": "force-merge", | ||
| "max-num-segments": 1 |
There was a problem hiding this comment.
Can you please also add request-timeoutand set it to a value that is high enough (I guess 7200 (2 hours) should suffice) to ensure we'll wait long enough for this operation to finish? Otherwise we might run queries while the force merge is still ongoing in the background.
There was a problem hiding this comment.
@danielmitterdorfer Thanks for the feedback. Addressed in 77faa8b
|
@danielmitterdorfer we would like to see these benchmarks starting from ES 7.6. For this, should I backport this PR to |
@mayya-sharipova yes, that would do the trick. :) |
Measure the performance of sort operations after force merging to 1 segment. PR elastic/elasticsearch#48533 adds a new merge policy that interleaves old and new segments on force merge. This checks the sort performance with this policy after docs are merged to 1 segment.
Measure the performance of sort operations
after force merging to 1 segment.
PR elastic/elasticsearch#48533 adds a new merge policy that interleaves old and new
segments on force merge. This checks the sort
performance with this policy after docs are merged to
1 segment.