-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Block requests sometimes take a lot of time #5831
Comments
0.7.32 includes the metrics added by #5811 and will be helpful to understand that |
I can now see on Grafana that the We've also deployed #5854 on two validator nodes, and I can see on these two nodes that the networking overhead is around a constant 200ms. This is actually pretty high in the absolute, and should also be fixed. I suppose it's because the network worker is quite busy. EDIT: the 200ms also include putting the response in the TCP buffer to send to the remote, which could explain it |
This does not explain the 40 second timeouts that happen all the time when syncing. Would be good to have a sync log for a machine that has |
Update: from the serving side, the fix to the "network freezes" seems to have improved the situation. I think the next step here would be to continue smoothing the network events-propagation/performances story, and see if it still happens afterwards. Even if the network events-propagation/performance issue is not directly responsible, fixing it first would eliminate the noise. |
I feel like this was caused by the network worker being overloaded. #6692 should considerably improve the situation. We'll see after it has been deployed. |
When syncing Kusama from scratch for example, one can see the sync speed go up and down a lot. The reason for that is that we spend a lot of time waiting for block responses.
This should be investigated.
The text was updated successfully, but these errors were encountered: