-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Closed
Labels
D1-mediumCan be fixed by a coder with good Rust knowledge but little knowledge of the codebase.Can be fixed by a coder with good Rust knowledge but little knowledge of the codebase.I5-enhancementAn additional feature request.An additional feature request.T1-FRAMEThis PR/Issue is related to core FRAME, the framework.This PR/Issue is related to core FRAME, the framework.
Description
The PoV benchmarking aims to estimate the worst-case scenario, which is unlikely to occur on average.
Too large over-estimations hurt block utilization. There is currently no way to retroactively measure the actual used proof size.
Having such a retroactive measurement in place would enable a multi iteration approach; alternating between dispatch and assessment phase to reach maximum block utilization.
It would therefore be nice to have a way to measure the weight of a batch of dispatchables after their execution. For example in:
- Scheduler Task dispatch
- XCM dispatch
- Transaction dispatch
- MessageQueue processing
Basically in every situation where we need to fit a batch of Dispatchables into a weight limit, and assume that the pre- and post-dispatch PoV weight differ greatly.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
D1-mediumCan be fixed by a coder with good Rust knowledge but little knowledge of the codebase.Can be fixed by a coder with good Rust knowledge but little knowledge of the codebase.I5-enhancementAn additional feature request.An additional feature request.T1-FRAMEThis PR/Issue is related to core FRAME, the framework.This PR/Issue is related to core FRAME, the framework.
Type
Projects
Status
done
Status
Done
Status
Done
Status
Done