-
Notifications
You must be signed in to change notification settings - Fork 337
[staking] reduce candidates bucket indexer storage #4622
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
base: master
Are you sure you want to change the base?
Conversation
message bucketList { | ||
uint64 maxBucket = 1; | ||
repeated uint64 deleted = 2; | ||
} |
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.
bucketList {
100
[]uint64{2, 3, 18}
}
means current max bucketID = 100, and bucket 2, 3, 18 are deleted, this is more efficient than storing all buckets
|
b = b3 | ||
d = []uint64{3, 4} | ||
} | ||
return nil, b, d, nil |
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.
this is only for test now, need to implement actual logic
Description
use versioned db to reduce candidates bucket indexer storage
Fixes #(issue)
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Test Configuration:
Checklist: