Improve Date Search Performance #977
Merged
Conversation
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
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## develop #977 +/- ##
========================================
Coverage 94.12% 94.12%
========================================
Files 238 238
Lines 15233 15235 +2
Branches 380 380
========================================
+ Hits 14338 14340 +2
Misses 515 515
Partials 380 380
|
alexanderkiel
force-pushed
the
improve-date-search-performance
branch
2 times, most recently
from
2bd89f9
to
6b38a22
Compare
Used indexes for equal, less than and starts after. That operators all have a predicate on the lower bound of the resource value that comes first in the index. The other operators can't use the existing index, because they either look at the upper bound or on both bounds. We have to add indexes in order to speed up the other operators. The issue is: #976.
alexanderkiel
force-pushed
the
improve-date-search-performance
branch
from
6b38a22
to
86e120b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Used indexes for equal, less than and starts after. That operators all have a predicate on the lower bound of the resource value that comes first in the index. The other operators can't use the existing index, because they either look at the upper bound or on both bounds.
We have to add indexes in order to speed up the other operators. The issue is: #976.
Performance documentation can be found here.