-
Notifications
You must be signed in to change notification settings - Fork 334
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
feat: memtable filter push down #2539
Conversation
I think we should add some benchmark for this feature. |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## develop #2539 +/- ##
===========================================
- Coverage 85.38% 85.01% -0.38%
===========================================
Files 737 737
Lines 117761 117916 +155
===========================================
- Hits 100553 100241 -312
- Misses 17208 17675 +467 |
I've run an informal test against this branch, it can improve by around 70% performance in scanning memtable. |
Cool. It would be beneficial for future improvements if we include a benchmark program in the repository. |
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.
LGTM
441bbc7
to
fe18dfb
Compare
* feat: memtable support filter pushdown to prune primary keys * fix: switch to next time series when pk not selected * fix: allow predicate evaluation failure * fix: some clippy warnings * fix: panic when no primary key in schema * feat: cache decoded record batch for primary key * refactor: use arcswap instead of rwlock * fix: format toml
I hereby agree to the terms of the GreptimeDB CLA
What's changed and what's your intention?
This PR enables filter pushdown for memtable so that irrelavant time series can be skipped.
Checklist
Refer to a related PR or issue link (optional)