-
Notifications
You must be signed in to change notification settings - Fork 25k
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
ExitableDirectoryReader slowdowns intensive points and terms query #53496
Labels
blocker
>regression
:Search/Search
Search-related issues that do not fall into other categories
v7.7.0
Comments
jimczi
added
>regression
blocker
:Search/Search
Search-related issues that do not fall into other categories
v7.7.0
labels
Mar 12, 2020
Pinging @elastic/es-search (:Search/Search) |
matriv
added a commit
to matriv/elasticsearch
that referenced
this issue
Mar 18, 2020
Check for cancellation every 1024 docs instead of every 15 to lower the impact of the check in query's performance. Fixes: elastic#53496
matriv
added a commit
to matriv/elasticsearch
that referenced
this issue
Mar 23, 2020
Benchmarking showed that the effect of the ExitableDirectoryReader is reduced considerably when checking every 4095 docs. Moreover, set the cancellable task before calling QueryPhase.preProcess() and make sure we don't wrap with an ExitableDirectoryReader at all when lowLevelCancellation() is set to false to avoid completely any performance impact. Follows: elastic#52822 Follows: elastic#53166 Follows: elastic#53496
matriv
added a commit
that referenced
this issue
Mar 23, 2020
Benchmarking showed that the effect of the ExitableDirectoryReader is reduced considerably when checking every 8191 docs. Moreover, set the cancellable task before calling QueryPhase#preProcess() and make sure we don't wrap with an ExitableDirectoryReader at all when lowLevelCancellation is set to false to avoid completely any performance impact. Follows: #52822 Follows: #53166 Follows: #53496
matriv
added a commit
that referenced
this issue
Mar 23, 2020
Benchmarking showed that the effect of the ExitableDirectoryReader is reduced considerably when checking every 8191 docs. Moreover, set the cancellable task before calling QueryPhase#preProcess() and make sure we don't wrap with an ExitableDirectoryReader at all when lowLevelCancellation is set to false to avoid completely any performance impact. Follows: #52822 Follows: #53166 Follows: #53496 (cherry picked from commit cdc377e)
38 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
blocker
>regression
:Search/Search
Search-related issues that do not fall into other categories
v7.7.0
The exitable directory reader added in #52822 seems to slowdown queries that uses points (
range
queries) and terms dictionary (terms
ad multi-term queries) intensively. These slowdowns have been spotted in our nightly runs as outlined here.We open this issue to discuss the best ways to mitigate these slowdowns. The first thing we'd like to try is to make the interval at which we check for cancellation or timeout smaller since we started with a relatively low value (15).
The text was updated successfully, but these errors were encountered: