All Questions
6 questions
6
votes
1
answer
118
views
cannot create module: instance allocation for this module requires 74376 bytes which exceeds the configured maximum of 65536 bytes
Try in to benchmark node pallets after Polkadot upgrade from 0.9.36 to 0.9.38 and get cannot create module: instance allocation for this module requires 74376 bytes which exceeds the configured ...
- 198
4
votes
1
answer
60
views
How to benchmark a crate's WASM execution performance?
How to benchmark the code's WASM execution performance?
I wrote a crate and want to use it in the runtime.
I want to know its WASM execution time in ms. How can I get that?
- 11.2k
0
votes
1
answer
35
views
Use criterion for statistic driven benchmarking of Substrate pallets
Criterion version 0.4.0 seems to support WASM builds: https://www.tweag.io/blog/2022-03-03-criterion-rs/#first-class-wasm-support
Can we us it to benchmark extrinsics of Substrate pallets?
- 575
1
vote
1
answer
391
views
Cannot run benchmarking: "Did not find the benchmarking metadata."
I have problems with trying to benchmark my custom pallet. I tried different scenarios and received different errors:
Using the same binary:
I built my node with cargo build --release --features ...
- 269
1
vote
0
answers
69
views
Another Benchmarking Wasm error [closed]
I asked a similar question a month ago here, and the answer/explanation was found in a failing cargo t -p pallet-nft --features runtime-benchmarks command.
This time, the building part works, the ...
- 519
1
vote
1
answer
94
views
Benchmarking Wasm error
I am trying to do benchmarking for my pallet,but I get the following error:
Error executing and verifying runtime benchmark: Execution aborted due to trap: wasm trap: wasm `unreachable` instruction ...
- 519