-
Notifications
You must be signed in to change notification settings - Fork 265
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
feat: Uses BatchWithFlusher in iavl tree #807
Conversation
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.
LGTM thank you
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.
overall looks good to me, except why hard code the flushThreshold?
That's because I discussed with marko and we decide to hard code the value to be the best option based on benchmark result run on osmosis node |
+1 on @cool-develope comment. Given that |
@julienrbrt you fine with merging this and then i can make the changes. |
Works! We need changelogs as well to reflect some API breaks from here in the follow-up |
@Mergifyio backport release/1.x.x |
❌ No backport have been created
GitHub error: |
@Mergifyio backport release/v1.x.x |
@Mergifyio backport release/v1.x.x |
✅ Backports have been created
|
(cherry picked from commit b42a0bc)
Co-authored-by: khanh-notional <[email protected]>
This PR replace the use of normal dbm.Batch with BatchWithFlusher in iavl tree
It also hard code the value of flushthreshold to 100KB