This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
Collation fetching times out too often #3748
Labels
I10-optimisation
An enhancement to provide better overall performance in terms of time-to-completion for a task.
Note: I am talking here about the soft timeout in collation fetching, which triggers another parallel download. Although we got reports about the network timeout to also hit some parachains.
See also #3230 and #3741
We should investigate, why collation fetching is taking way longer than expected. One simple reason that comes to mind, is that multiple validators all request from the same collator, thus their requests will be queued, together with multiple heads this could easily lead to several hundreds of milliseconds.
Assuming that there is only a single collator having the collation, the current behavior could actually be fine, as there is no way to improve throughput. In case, there is another collator, it would be way better for the collator to immediately cancel incoming requests once it has 1 queued already (queue size one), so the validator can immediately move on the the next collator, not wasting any time.
For this to work properly, we not only need to set queue size to 1, but also change behavior of validators to not change the collators reputation in the event of a single cancel, as this is now expected behavior - see #3230 .
The text was updated successfully, but these errors were encountered: