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

Memory issues during genesis sync #3730

Open
michaelsproul opened this issue Nov 15, 2022 · 1 comment
Open

Memory issues during genesis sync #3730

michaelsproul opened this issue Nov 15, 2022 · 1 comment
Labels
optimization Something to make Lighthouse run more efficiently. syncing

Comments

@michaelsproul
Copy link
Member

Description

MigaLabs and now Gnosis have both reported Lighthouse using a lot of memory during genesis sync. We thought it might have been #2944, but with that issue resolved the problem is still occurring.

Looking at some metrics on the affected Gnosis servers it seems not to be a memory fragmentation issue, as the non-mmap memory is high (~10GB) and the free block memory is low (<800MB). I think to get to the bottom of this we would need to run lighthouse under heaptrack while syncing from genesis on mainnet or Gnosis chain.

Version

v3.2.1

Workarounds

Use checkpoint sync. It's a lot faster in multiple ways and unaffected by this issue.

There will be some checkpoint sync servers set up for Gnosis chain before the Gnosis merge.

@michaelsproul michaelsproul added syncing optimization Something to make Lighthouse run more efficiently. labels Nov 15, 2022
@michaelsproul
Copy link
Member Author

May be alleviated by #3697. It would be interesting to compare GNU malloc vs jemalloc during genesis sync

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
optimization Something to make Lighthouse run more efficiently. syncing
Projects
None yet
Development

No branches or pull requests

1 participant