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

WorldState resync takes too long on some good setups #6369

Open
ahamlat opened this issue Jan 8, 2024 · 0 comments
Open

WorldState resync takes too long on some good setups #6369

ahamlat opened this issue Jan 8, 2024 · 0 comments
Labels
P3 Medium (ex: JSON-RPC request not working with a specific client library due to loose spec assumtion) performance syncing

Comments

@ahamlat
Copy link
Contributor

ahamlat commented Jan 8, 2024

Description

Some users reported very slow resync time on the world state when using this curl command :

curl -X POST --data '{"jsonrpc":"2.0","method":"debug_setHead","params":["0x1211F34"],"id":1}' http://localhost:8545

Example
On a 2 TB A-Data XPG SX8200 Pro, it took 15.5 hours, with Besu running on Docker.

Expected behavior: [What you expect to happen]
WorldState resync should take predictable time regarding the used hardware.

Actual behavior: [What actually happens]
Sometimes worldstate resync takes too long even on good setups

Frequency: [What percentage of the time does it occur?]
Hard to say, we've seen some users reporting this behaviour recently.

@non-fungible-nelson non-fungible-nelson added performance syncing P3 Medium (ex: JSON-RPC request not working with a specific client library due to loose spec assumtion) labels Jan 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P3 Medium (ex: JSON-RPC request not working with a specific client library due to loose spec assumtion) performance syncing
Projects
None yet
Development

No branches or pull requests

2 participants