[DNM] asset-hub-kusama: use inmemorydb weights #918
Conversation
Modify asset-hub-kusama to use the read/write costs in validate block on validator reference hardware, since these are weights that guarantee the blocks will pass validation and make it on the relay chain. This were obtained with the benchmark created here: paritytech/polkadot-sdk#8069. Part of: paritytech/polkadot-sdk#6131 Fixes: polkadot-fellows#800 Signed-off-by: Alexandru Gheorghe <alexandru.gheorghe@parity.io>
Signed-off-by: Alexandru Gheorghe <alexandru.gheorghe@parity.io>
|
How big of a change is this? I would like to avoid including big changes with the AHM runtime upgrade since we will do AHM Kusama very soon. |
@ggwpez, The whole point of this change is improving throughput for the SCC launch, which is after AHM migration, so I would say it can be merged after AHM Kusama happens. |
|
if not urgent, let merge this after the AHM release. if this merged we need to adjust some weights on RC side (control flow mechanics accounting for AH weights) and test it. |
ACK, marked it as DNM so that it merges after AHM release. |
alexggh
changed the title
Signed-off-by: Alexandru Gheorghe <alexandru.gheorghe@parity.io>
6 participants
Modify asset-hub-kusama to use the read/write costs computed in validate block on validator reference hardware, since these are weights that guarantee the blocks will pass validation and make it on the relay chain.
This were obtained with the benchmark created here: paritytech/polkadot-sdk#8069.
Part of: #800