-
Notifications
You must be signed in to change notification settings - Fork 20k
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
cmd/geth, ethdb/pebble: improve database statistic #29948
Conversation
I am considering whether we should return all database statistics instead of just one particular property. From a UX perspective, it is nearly impossible for users to know which database properties are available for dumping. Additionally, LevelDB and Pebble have different statistic definitions, which could add more complexity. Will discuss with team and turn this pull request into a meaningful improvement. |
by the way, if geth still support leveldb then it's still valid to re-open this PR #25154 ? |
We want to drop leveldb, but I'm guessing anyone who runs an arhcive node might have it in leveldb due to thesheer time it takes to resync. So will drop leveldb when we ship pathdb archive. But we don't want to expand on it. |
Leveldb statistics
Pebble statistics
|
No description provided.