-
Notifications
You must be signed in to change notification settings - Fork 1k
[wip] Fix PoV size reclaim #9924
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: mku-pov-poc-base
Are you sure you want to change the base?
Conversation
This is a first step into fixing #6020. The underlying problem for parachains is that when calling `storage_root`, values that are written, will need to be looked up in the trie. This is required to insert the value or to remove it. The problem is that this lookup in `storage_root` increases the storage proof size, but storage reclaim for example can not track these lookups. This means that with storage reclaim it is possible to include more transactions than what the block should be allowed to include. This pull request reads a key from the backend the first time it is written. This results in taking into account what `storage_root` is doing at the end of a block. However, this may still skips reading one extra `node` (depending on the trie structure). Skipping only one `node` is far less problematic than skipping the entire lookup. A future pull request will improve this further to take the entire operation of `storage_root` into account. For chains that are not recording a storage proof, they will still do this extra backend read. However, this read will end up in the cache. At the end of the block the key will be read again as part of `storage_root`, but served from the cache. So, there is no downside of this.
This reverts commit 4f00caf.
/cmd bench --help |
Command help:
|
/cmd bench --runtime asset-hub-westend |
Command "bench --runtime asset-hub-westend" has started 🚀 See logs here |
Command "bench --runtime asset-hub-westend" has failed ❌! See logs here |
/cmd bench --runtime asset-hub-westend |
Command "bench --runtime asset-hub-westend" has started 🚀 See logs here |
Command "bench --runtime asset-hub-westend" has failed ❌! See logs here |
/cmd bench --runtime asset-hub-westend |
Command "bench --runtime asset-hub-westend" has started 🚀 See logs here |
Command "bench --runtime asset-hub-westend" has finished ✅ See logs here Subweight results:
Command output:✅ Successful benchmarks of runtimes/pallets: |
All GitHub workflows were cancelled due to failure one of the required jobs. |
No description provided.