-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
Search - enable low_level_cancellation by default. #42291
Conversation
Pinging @elastic/es-search |
Benchmarks were conducted using Rally with the following settings:
Despite these settings, the expected slow-down in LLC:on versus LLC:off failed to show up in test results. If anything the LLC:on results were observed to be faster (?!). It should be noted that even within runs using the same settings there were variable result timings which suggests some environmental issues running repeated tests. Despite this, the trend seems to show that LLC:on is faster than LLC:off which is counter-intuitive. ConclusionIdeally we would have clearly demonstrated our expectations that LLC:on added a small but acceptable overhead to search performance. Instead we seem to see a variety of timings which if anything suggest LLC:on makes things faster. This is a little baffling but my assumption is that we should enable it by default and keep an eye on nightly benchmarks. |
test this please |
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.
The diff is simple, but this required lots of testing. Thanks @markharwood for looking into this!
Benchmarking on worst-case queries (max agg on match_all or popular-term query with large index) was not noticeably slower. Closes elastic#26258
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.
Thanks for all the testing! LGTM
Benchmarking on worst-case queries (max agg on match_all or popular-term query with large index) was not noticeably slower. Closes elastic#26258
Benchmarking on worst-case queries (max agg on match_all or popular-term query with large index) was not noticeably slower. Closes elastic#26258
Benchmarking on worst-case queries (max agg on match_all or popular-term query with large index) was not noticeably slower.
Closes #26258