kv: add periodic table size metrics and logs#16104
Merged
Merged
Conversation
AskAlexSharov
pushed a commit
that referenced
this pull request
Jul 15, 2025
relates to #16104 adds a prune duration metric
AskAlexSharov
approved these changes
Jul 15, 2025
AskAlexSharov
pushed a commit
that referenced
this pull request
Jul 16, 2025
to help us see time spent per stage - can further help with #16104
2 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
in bloatnet we're exploding the chaindata db size up to 500GB on chain tip - something is not right
this PR aims to make it easy to see what is happening by adding periodic table size metric collection for grafana chart and debug logs (collect every 5 mins - configurable)