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

Drastic increase in snapshot initialization time #860

Closed
the-smooth-operator opened this issue Oct 1, 2024 · 2 comments
Closed

Drastic increase in snapshot initialization time #860

the-smooth-operator opened this issue Oct 1, 2024 · 2 comments

Comments

@the-smooth-operator
Copy link

Time to start a fresh node from snapshot has quickly degraded.
Pre spring snapshot initialization time was about 20 mins. Post spring, up until today we were at about 15 minutes for a 8GB+ snapshots.
Today, snapshot initialization (about 11G/snapshot) seems to last for several hours even in top hardware.

We see a lot of IO:
image

However disk size stops to increase always at about 90 to 100GB of disk size:
image

Logs show slow process and only messages like:
info 2024-10-01T21:41:49.884 nodeos controller.cpp:2435 operator() ] Snapshot initialization 72% complete

@the-smooth-operator
Copy link
Author

We have noticed that increasing the total available memory helps. However, the process never utilizes all the memory available.
I.e: if we set a limit of 16Gi of memory we only the process using up to see 2Gi.

@bhazzard
Copy link

Given that the state database has recently multiplied in size, 16GB memory is not sufficient. 192GB minimum, 256GB recommended for nodes with the simplest configuration. If you have sys-admin skills you can get away with significantly lower memory by utilizing tmpfs with swap file.

Some other config options that can help run in the most efficient way:
read-mode=irreversible
validation-mode=light
eos-vm-oc-enable=true

@github-project-automation github-project-automation bot moved this from Todo to Done in Team Backlog Oct 17, 2024
@bhazzard bhazzard removed the triage label Oct 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

3 participants