-
Notifications
You must be signed in to change notification settings - Fork 55
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
Investigate slow full sync #2294
Comments
corverroos
added a commit
that referenced
this issue
Oct 28, 2024
Add `eta` and `bps` metrics to logs. issue: #2294
corverroos
added a commit
that referenced
this issue
Oct 28, 2024
Show cpu and net rx container stats. issue: #2294
corverroos
added a commit
that referenced
this issue
Oct 28, 2024
SyncProgress returns nil when synced. issue: #2294
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem to Solve
Reports from operators indicate that syncing omega can take more than 24 hours. Our
join-omega-nightly
also timed out after 6 hours.We need to figure out why syncing is slow, or more precisely, what can one expect in terms of blocks/s when syncing? We also need to figure out of this is impacted by peers? Are some peers slower than others?
Proposed Solution
Pushing metrics to grafana is a good idea, but metrics unfortunately don’t show which peers we are syncing from.
I think that would be the next thing to do. During
join-omega-nightly
somehow figure out what peers we are syncing from and the network bandwidth being used from that peer (network bandwidth per IP).The text was updated successfully, but these errors were encountered: