Skip to content

Process PeerViewChange messages with priority #577

@sandreim

Description

@sandreim

This will need some flavor of paritytech/orchestra#8 implemented first.

Prioritising the processing of PeerViewChange in networking subsystems will help reducing wasteful/useless work and faster propagation of gossip messages - approvals/assignments, bitfields and statements.

We know that under high load, these messages usually have a very high ToF (up to 5s) and get processed very late by the approval distribution subsystem. With this change the peer view update is processed ahead of all other messages except signals.

Metadata

Metadata

Assignees

Labels

I9-optimisationAn enhancement to provide better overall performance in terms of time-to-completion for a task.

Type

No type
No fields configured for issues without a type.

Projects

Status
Completed

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions