Skip to content
Snippets Groups Projects
Unverified Commit 86dc1ab3 authored by Alexandru Gheorghe's avatar Alexandru Gheorghe Committed by GitHub
Browse files

bitfield_distribution: Move on blocking pool and use custom capacity (#5787)


## Description

Details and rationale explained here:
https://github.com/paritytech/polkadot-sdk/issues/5657#issuecomment-2363076080

Fixes: https://github.com/paritytech/polkadot-sdk/issues/5657

---------

Signed-off-by: default avatarAlexandru Gheorghe <alexandru.gheorghe@parity.io>
parent 2e4e5bf2
Branches
No related merge requests found
Pipeline #498253 waiting for manual action with stages
in 1 hour, 5 minutes, and 38 seconds
......@@ -521,7 +521,7 @@ pub struct Overseer<SupportsParachains> {
])]
bitfield_signing: BitfieldSigning,
#[subsystem(BitfieldDistributionMessage, sends: [
#[subsystem(blocking, message_capacity: 8192, BitfieldDistributionMessage, sends: [
RuntimeApiMessage,
NetworkBridgeTxMessage,
ProvisionerMessage,
......
title: "Move bitfield_distribution to blocking task pool and set capacity to 8192"
doc:
- audience: Node Dev
description: |
This is moving bitfield_distribution to the blocking task pool because it does cpu
intensive work and to make it snappier. Additionally, also increase the message
capacity of the subsystem to make sure the queue does not get full if there is a
burst of messages.
crates:
- name: polkadot-overseer
bump: patch
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment