[Don't merge] Benchmark current contracts pallet#8608
Conversation
|
/benchmark runtime pallet pallet_contracts |
|
Finished benchmark for branch: at-rebench Benchmark: Benchmark Runtime Pallet cargo run --release --features=runtime-benchmarks --manifest-path=bin/node/cli/Cargo.toml -- benchmark --chain=dev --steps=50 --repeat=20 --pallet=pallet_contracts --extrinsic="*" --execution=wasm --wasm-execution=compiled --heap-pages=4096 --output=./frame/contracts/src/weights.rs --template=./.maintain/frame-weight-template.hbs ResultsPallet: "pallet_contracts", Extrinsic: "on_initialize", Lowest values: [], Highest values: [], Steps: [50], Repeat: 20
|
…/node/cli/Cargo.toml -- benchmark --chain=dev --steps=50 --repeat=20 --pallet=pallet_contracts --extrinsic=* --execution=wasm --wasm-execution=compiled --heap-pages=4096 --output=./frame/contracts/src/weights.rs --template=./.maintain/frame-weight-template.hbs
| fn instrument(c: u32, ) -> Weight { | ||
| (29_918_000 as Weight) | ||
| // Standard Error: 185_000 | ||
| .saturating_add((123_774_000 as Weight).saturating_mul(c as Weight)) | ||
| (0 as Weight) | ||
| // Standard Error: 242_000 | ||
| .saturating_add((2_317_462_000 as Weight).saturating_mul(c as Weight)) | ||
| .saturating_add(T::DbWeight::get().reads(1 as Weight)) | ||
| .saturating_add(T::DbWeight::get().writes(1 as Weight)) | ||
| } |
There was a problem hiding this comment.
The increased instrument costs are already on master. Not sure what caused this issue. Maybe an updated pwasm-utils?
|
Weight regression fixed by #8655 |
Re-Benchmark current master of the contracts pallet in order to find out if the high instrumentation costs are already on master or are introduces by the said PR.