-
Notifications
You must be signed in to change notification settings - Fork 323
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: avoid cache during compaction #5135
Conversation
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
Documentation and Community
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #5135 +/- ##
=======================================
Coverage 84.03% 84.04%
=======================================
Files 1168 1168
Lines 217572 217640 +68
=======================================
+ Hits 182841 182916 +75
+ Misses 34731 34724 -7 |
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
Nit: If there was a NoopCacheManager, we wouldn't need to modify so much code. |
I hereby agree to the terms of the GreptimeDB CLA.
Refer to a related PR or issue link (optional)
What's changed and what's your intention?
This pr fixes the memory consumption issue during log ingestion. From prior benchmark, we observed unexpected memory usage which won't be reclaimed even after stopping benchmark and flushing all pending data to disk.
In memory profiling we can see that it's related to merge reader that caches row group data. This behavior is necessary in normal query paths, but not desired in compaction, in that the files read during compaction will be deleted shortly after compaction.
This can also be confirmed through metrics:
Memory usage after this fix
Checklist