-
Notifications
You must be signed in to change notification settings - Fork 741
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
revive sub-du
in utils/frame
#449
Comments
@harrysolovay has build this with CAPI: https://github.com/paritytech/capi/blob/main/examples/size_tree.ts |
Please see: #4341 (review) |
@kianenigma sounds like we should close this issue and create a new one for the subxt explorer? I think also @josepot at some point added/wanted to add something similar to papi? |
Noice 🚀 If it works on the basis of try-runtime, I would say it could come and live here in the sdk, but if not, it can also somewhere in your gh. Would be good if you share the link here + result of running it on DOT and KSM relay chains. |
Code is here now, did not check in detail yet: https://github.com/ggwpez/pdu |
EDIT: There's already a PR open to build upon, with some comments.
I am suggesting that we bring sub-du, originally implemented with rust and using an older version of metadata here:
https://github.com/paritytech/substrate-debug-kit/blob/master/sub-du/src/main.rs
back to substrate. This can be a useful tool to report the state size of any substrate based chain.
Notes:
jsonrpsee
client.chain-spec-builder
andsubkey
here so that we prevent breaking changes.cc @ggwpez I was told you would also be interested in this, perhaps for try-runtime diagnosis.
Example output from 2020:
The text was updated successfully, but these errors were encountered: