-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Conversation
/benchmark runtime polkadot frame_system |
Finished benchmark for branch: shawntabrizi-new-system-weights Benchmark: Benchmark Runtime Polkadot Pallet cargo run --release --features=runtime-benchmarks -- benchmark --chain=polkadot-dev --steps=50 --repeat=20 --pallet=frame_system --extrinsic="*" --execution=wasm --wasm-execution=compiled --heap-pages=4096 --header=./file_header.txt --output=./runtime/polkadot/src/weights/ ResultsPallet: "frame_system", Extrinsic: "remark", Lowest values: [], Highest values: [], Steps: [50], Repeat: 20
|
…n=polkadot-dev --steps=50 --repeat=20 --pallet=frame_system --extrinsic=* --execution=wasm --wasm-execution=compiled --heap-pages=4096 --header=./file_header.txt --output=./runtime/polkadot/src/weights/
I reran the benchmarks and looked at the raw results, the effect of the linear increase on the hash function overtakes any constant weight component. From the eyes of the min squares analysis, a best fit of 0 constant value is right. This should be fine since we add to any weight the "base weight" of a call, so a remark of no bytes will still have a weight, but yeah results are not exactly perfect |
Follow up to: #2541