mirror of
https://github.com/pezkuwichain/pezkuwi-subxt.git
synced 2026-04-26 13:27:57 +00:00
47e46d178b
Introduce a new test objective : `DataAvailabilityWrite`. The new benchmark measures the network and cpu usage of `availability-distribution`, `biftield-distribution` and `availability-store` subsystems from the perspective of a validator node during the process when candidates are made available. Additionally I refactored the networking emulation to support bandwidth acounting and limits of incoming and outgoing requests. Screenshot of succesful run <img width="1293" alt="Screenshot 2024-01-17 at 19 17 44" src="https://github.com/paritytech/polkadot-sdk/assets/54316454/fde11280-e25b-4dc3-9dc9-d4b9752f9b7a"> --------- Signed-off-by: Andrei Sandu <andrei-mihail@parity.io>
16 lines
735 B
Plaintext
16 lines
735 B
Plaintext
# Schema: Polkadot SDK PRDoc Schema (prdoc) v1.0.0
|
|
# See doc at https://raw.githubusercontent.com/paritytech/polkadot-sdk/master/prdoc/schema_user.json
|
|
|
|
title: Add `availability-distribution` and `biftield-distribution` subsystem benchmark
|
|
|
|
doc:
|
|
- audience: Node Dev
|
|
description: |
|
|
The new subsystem benchmark test objective (`DataAvailabilityWrite`) is designed to stress
|
|
test the part of the pipeline that takes as input a backed candidate and then distributes
|
|
it as erasure coded chunks to other validators. The test pulls in the `av-store`,
|
|
`bitfield-distribution` and `availability-distribution` subsystems while the whole network and rest
|
|
of the node subsystems are emulated.
|
|
|
|
crates: [ ]
|