-
Notifications
You must be signed in to change notification settings - Fork 215
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
[Merged by Bors] - sync2: fptree: don't get next in FingerprintInterval if not needed #6558
Conversation
ff8684a
to
a0aea57
Compare
Retrieving the next item when fingerprinting an interval is only useful during slow splitting, when we need to split a range but "easy split" (involving only in-memory FPTree) fails. In other cases, the next item is not really needed and getting it may incur an unwanted database access. This also fixes intermittent failures of TestFPTreeManyItems test.
a0aea57
to
fca7843
Compare
Codecov ReportAttention: Patch coverage is
✅ All tests successful. No failed tests found.
Additional details and impacted files@@ Coverage Diff @@
## develop #6558 +/- ##
=======================================
Coverage 79.8% 79.8%
=======================================
Files 354 354
Lines 47015 47023 +8
=======================================
+ Hits 37534 37556 +22
+ Misses 7351 7343 -8
+ Partials 2130 2124 -6 ☔ View full report in Codecov by Sentry. |
bors merge |
…6558) ## Motivation Retrieving the next item (one immediately following the fingerprinted interval) when fingerprinting an interval is only useful during slow splitting, when we need to split a range but "easy split" (involving only in-memory FPTree) fails. In other cases, the next item is not really needed and getting it may incur an unwanted database access. `TestFPTreeManyItems` fails intermittently when it happens to fingerprint an empty range during random testing due to a problem with handling next items.
Build failed: |
Unrelated
|
bors merge |
…6558) ## Motivation Retrieving the next item (one immediately following the fingerprinted interval) when fingerprinting an interval is only useful during slow splitting, when we need to split a range but "easy split" (involving only in-memory FPTree) fails. In other cases, the next item is not really needed and getting it may incur an unwanted database access. `TestFPTreeManyItems` fails intermittently when it happens to fingerprint an empty range during random testing due to a problem with handling next items.
Pull request successfully merged into develop. Build succeeded: |
Motivation
Retrieving the next item (one immediately following the fingerprinted interval) when fingerprinting an interval is only useful during slow splitting, when we need to split a range but "easy split" (involving only in-memory FPTree) fails. In other cases, the next item is not really needed and getting it may incur an unwanted database access.
TestFPTreeManyItems
fails intermittently when it happens to fingerprint an empty range during random testing due to a problem with handling next items.Description
This removes unneeded retrieval of the next item and fixes
TestFPTreeManyItems
.