Skip to content
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

go.mod : goleveldb Reduce memory allocation #23417

Merged
merged 1 commit into from
Aug 24, 2021
Merged

Conversation

ucwong
Copy link
Contributor

@ucwong ucwong commented Aug 19, 2021

Reduce memory allocation of buffer_pool and db
syndtr/goleveldb#367

snappy-4.0.0 upgrade
syndtr/goleveldb#365

Copy link
Member

@MariusVanDerWijden MariusVanDerWijden left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM
Replacing the weird bufferpool with a sync.Pool was something that I also took a stab at some time ago. This could significantly decrease mem allocs.
Updating Snappy to 0.0.4 is also a good change (we didn't update yet because there's no real difference between 0.0.3 and 0.0.4 only testing updates and more inclusive language)

@ligi
Copy link
Member

ligi commented Aug 24, 2021

Thanks - this looks good and will most likely be merged - we just need to run it to see the actual improvements - or did you do some benchmarks by any chance?

@karalabe karalabe added this to the 1.10.9 milestone Aug 24, 2021
@karalabe karalabe merged commit fe2f153 into ethereum:master Aug 24, 2021
sidhujag pushed a commit to sidhujag/go-ethereum that referenced this pull request Aug 25, 2021
maoueh pushed a commit to streamingfast/go-ethereum that referenced this pull request Nov 29, 2021
maoueh pushed a commit to streamingfast/go-ethereum that referenced this pull request Jan 31, 2022
yongjun925 pushed a commit to DODOEX/go-ethereum that referenced this pull request Dec 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants