mirror of https://github.com/pezkuwichain/pezkuwi-subxt.git synced 2026-04-26 01:47:55 +00:00

Files

T

Oliver Tale-Yazdi c36c51cac3 bench pallet: only require Hash instead of Block (#3244 )

Preparation for https://github.com/paritytech/polkadot-sdk/issues/2664

Changes:
- Only require `Hash` instead of `Block` for the benchmarking
- Refactor DB types to do the same

## Integration

This breaking change can easily be integrated into your node via:  
```patch
- cmd.run::<Block, ()>(config)
+ cmd.run::<HashingFor<Block>, ()>(config)
```

Status: waiting for CI checks

---------

Signed-off-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io>
Co-authored-by: Bastian Köcher <git@kchr.de>
Co-authored-by: cheme <emericchevalier.pro@gmail.com>

2024-02-08 17:27:52 +00:00

src

bench pallet: only require Hash instead of Block (#3244 )

2024-02-08 17:27:52 +00:00

build.rs

Remove years from copyright notes. (#13415 )

2023-02-21 18:46:41 +00:00

Cargo.toml

Sync Cargo.toml and crates.io versions (#3034 )

2024-01-26 18:14:03 +00:00

README.md

Markdown linter (#1309 )

2023-09-04 12:02:32 +03:00

README.md

The Benchmarking CLI

This crate contains commands to benchmark various aspects of Substrate and the hardware. All commands are exposed by the Substrate node but can be exposed by any Substrate client. The goal is to have a comprehensive suite of benchmarks that cover all aspects of Substrate and the hardware that its running on.

Invoking the root benchmark command prints a help menu:

$ cargo run --profile=production -- benchmark

Sub-commands concerned with benchmarking.

USAGE:
    substrate benchmark <SUBCOMMAND>

OPTIONS:
    -h, --help       Print help information
    -V, --version    Print version information

SUBCOMMANDS:
    block       Benchmark the execution time of historic blocks
    machine     Command to benchmark the hardware.
    overhead    Benchmark the execution overhead per-block and per-extrinsic
    pallet      Benchmark the extrinsic weight of FRAME Pallets
    storage     Benchmark the storage speed of a chain snapshot

All examples use the production profile for correctness which makes the compilation very slow; for testing you can use --release. For the final results the production profile and reference hardware should be used, otherwise the results are not comparable.

The sub-commands are explained in depth here:

block Compare the weight of a historic block to its actual resource usage
machine Gauges the speed of the hardware
overhead Creates weight files for the Block- and Extrinsic-base weights
pallet Creates weight files for a Pallet
storage Creates weight files for Read and Write storage operations

License: Apache-2.0