-
Notifications
You must be signed in to change notification settings - Fork 53
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
perf: Add support for range spans #86
Conversation
!!!!! - find and use parent prefix and then add filter(s) to the query objectdefradb/datastores/iterable_transaction_shim.go Lines 65 to 70 in 2d6e7ab
This comment was generated by todo based on a
|
4979346
to
3fbe92c
Compare
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.
All looks pretty good. very minor comments/clarification.
a79d683
to
b93bc96
Compare
2d6e7ab
to
b323c93
Compare
Codecov Report
@@ Coverage Diff @@
## develop #86 +/- ##
===========================================
+ Coverage 58.71% 58.76% +0.05%
===========================================
Files 89 89
Lines 8531 8578 +47
===========================================
+ Hits 5009 5041 +32
- Misses 2980 2993 +13
- Partials 542 544 +2
|
Benchmarks look similar to dev, with some probable improvements in read speed (dev results are from a few hours ago (actually on the multi-scan branch), so maybe don't read to much into it, other than it is not significantly worse): Benchmarks from branch:
From develop:
|
b323c93
to
d58f033
Compare
* Correctly prefix dockey filter's span end * Add support for range spans
* Correctly prefix dockey filter's span end * Add support for range spans
Closes #64
It is harder than it needs to be to test the range-span stuff as we don't yet have the functionality that uses it, so I have left the complicated part of the shim unimplemented - it can be done in the ticket that would use this system (then it can be properly tested by swapping the badger ds in the utils class for the map ds).
I couldnt find a way to retarget a PR, so if/when the parent branch gets merged and if people are happy with the proposed changes I'll create a new non-draft PR against develop.