chore: add more metrics about parquet and cache
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?
as title
useful for diagnosing slow queries
Checklist
- [ ] I have written the necessary rustdoc comments.
- [ ] I have added the necessary unit tests and integration tests.
- [ ] This PR requires documentation updates.
Summary by CodeRabbit
-
New Features
- Introduced a cache eviction metric for improved monitoring of cache performance.
- Added a histogram metric to measure the time taken for loading Parquet metadata.
-
Improvements
- Enhanced observability of cache eviction reasons for better diagnostics.
- Implemented performance tracking in the MetadataLoader for metadata loading efficiency.
[!IMPORTANT]
Review skipped
Auto reviews are disabled on this repository.
Please check the settings in the CodeRabbit UI or the
.coderabbit.yamlfile in this repository. To trigger a single review, invoke the@coderabbitai reviewcommand.You can disable this status message by setting the
reviews.review_statustofalsein the CodeRabbit configuration file.
Walkthrough
The recent changes improve the caching system's monitoring capabilities by adding metrics for cache evictions and performance tracking during Parquet metadata loading. The CacheManagerBuilder now logs eviction reasons more effectively, while new metrics provide insights into cache behavior and loading efficiency. These enhancements allow developers to better diagnose performance issues, leading to improved overall system observability.
Changes
| Files | Change Summary |
|---|---|
src/cache.rs |
Enhanced CacheManagerBuilder to include CACHE_EVICTION metric for improved logging of eviction causes. |
src/mito2/src/metrics.rs |
Introduced CACHE_EVICTION counter and PARQUET_METADATA_LOAD_ELAPSED histogram for monitoring cache evictions and metadata loading times. |
src/sst/parquet/metadata.rs |
Added performance monitoring in MetadataLoader for Parquet metadata loading using the new histogram metric. |
Poem
🐇 In the meadow where bunnies play,
Metrics bloom in a lively array.
Evictions tracked with a hop and a cheer,
Loading data faster, the path is now clear!
Cache and metadata, a dance so bright,
Observability shines in the soft moonlight! ✨
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?
Tips
Chat
There are 3 ways to chat with CodeRabbit:
- Review comments: Directly reply to a review comment made by CodeRabbit. Example:
I pushed a fix in commit <commit_id>.Generate unit testing code for this file.Open a follow-up GitHub issue for this discussion.
- Files and specific lines of code (under the "Files changed" tab): Tag
@coderabbitaiin a new review comment at the desired location with your query. Examples:@coderabbitai generate unit testing code for this file.@coderabbitai modularize this function.
- PR comments: Tag
@coderabbitaiin a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:@coderabbitai generate interesting stats about this repository and render them as a table.@coderabbitai show all the console.log statements in this repository.@coderabbitai read src/utils.ts and generate unit testing code.@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.@coderabbitai help me debug CodeRabbit configuration file.
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 as PR comments)
@coderabbitai pauseto pause the reviews on a PR.@coderabbitai resumeto resume the paused reviews.@coderabbitai reviewto trigger an incremental review. This is useful when automatic reviews are disabled for the repository.@coderabbitai full reviewto do a full review from scratch and review all the files again.@coderabbitai summaryto regenerate the summary of the PR.@coderabbitai resolveresolve all the CodeRabbit review comments.@coderabbitai configurationto show the current CodeRabbit configuration for the repository.@coderabbitai helpto get help.
Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
CodeRabbit Configuration File (.coderabbit.yaml)
- You can programmatically configure CodeRabbit by adding a
.coderabbit.yamlfile to the root of your repository. - Please see the configuration documentation for more information.
- If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation:
# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json
Documentation and Community
- Visit our Documentation for detailed information on how to use CodeRabbit.
- Join our Discord Community to get help, request features, and share feedback.
- Follow us on X/Twitter for updates and announcements.
Codecov Report
Attention: Patch coverage is 89.65517% with 3 lines in your changes missing coverage. Please review.
Project coverage is 85.02%. Comparing base (
4cd5ec7) to head (85d6617). Report is 22 commits behind head on main.
Additional details and impacted files
@@ Coverage Diff @@
## main #4410 +/- ##
=======================================
Coverage 85.02% 85.02%
=======================================
Files 1075 1075
Lines 192542 192567 +25
=======================================
+ Hits 163709 163739 +30
+ Misses 28833 28828 -5
@v0y4g3r PTAL
@evenyag PTAL
@evenyag PTAL