mirror of https://github.com/pezkuwichain/pezkuwi-subxt.git synced 2026-06-26 10:01:13 +00:00

Files

T

Koute b1bbdf1192 Improve base weights consistency and make sure they're never zero (#11806 )

* Improve base weights consistency and make sure they're never zero

* Switch back to `linregress` crate; add back estimation errors

* Move the test into `mod tests`

* Use all of the samples instead of only the first one

* Use full precision extrinsic base weights and slopes

* Add an extra comment

* ".git/.scripts/bench-bot.sh" pallet dev pallet_contracts

Co-authored-by: parity-processbot <>
Co-authored-by: Shawn Tabrizi <shawntabrizi@gmail.com>

2022-09-14 16:01:13 +00:00

src

Improve base weights consistency and make sure they're never zero (#11806 )

2022-09-14 16:01:13 +00:00

build.rs

Follow ups for benchmark machine (#11270 )

2022-04-26 14:31:26 +00:00

Cargo.toml

Bump serde_json from 1.0.79 to 1.0.85 (#12079 )

2022-08-26 09:32:20 +02:00

README.md

Document benchmarking CLI (#11246 )

2022-05-25 03:47:21 +00: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