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.
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
add ancient.total_alive_bytes metric #2828
add ancient.total_alive_bytes metric #2828
Changes from all commits
81f85b9
50be7e0
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
I was initially curious how we guaranteed
slots
was all the ancient storages, otherwise this wouldn't be a 'total', per se.I see we get
slots
by calling AccountsDb::get_sorted_potential_ancient_slots(). I believe it is safe for this function to assume/require thatslots
is correct.And assuming we use 'pack', then the stats are reported after each invocation of combine_ancient_slots_packed(), so I think that also ensures we don't sum up multiple 'totals' too.