-
Notifications
You must be signed in to change notification settings - Fork 6
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
bump geth #39
base: master
Are you sure you want to change the base?
Conversation
github.com/dustinxie/gmsm v1.4.0 | ||
github.com/ethereum/go-ethereum v1.10.4 | ||
github.com/ethereum/go-ethereum v1.13.5-0.20240410090245-9dcf8aae4742 |
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 used the lastest commit in the master branch for testing, since geth v1.13.15 hasn't been released yet.
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.
For prod usage, we might wait until geth v1.13.15 is released
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.
can we just use v1.13.12 (which is the Cancun release version we use for iotex-core)
Does v1.13.12 fix this memory issue?
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.
no. pls check the geth's pr ethereum/go-ethereum@ab49f22, which isn't included in v1.13.14
pls check #40 before merging this |
PR purpose: optimization mem allocation by bumping crypto library in Geth
The memory allocation of pubkey deserialization is reduced by 70% in the PR
The results of benchmark test after and before commit