Optionally show storage entry's size

[dastansam]

Background

when looking at the storage size, it should be possible to calculate and show the size of it. See here and here

[jsdw]

So from a quick look at sub-du and those links I believe that the approach is:

• Fetch metadata
• Iterate over all storage items in it (https://github.com/paritytech/substrate-debug-kit/blob/e12503ab781e913735dc389865a3b8b4a6c6399d/sub-du/src/main.rs#L190)
• Create a storage key for the root of each storage item and then call the "state_getStorageSize" RPC method (https://github.com/paritytech/substrate-debug-kit/blob/e12503ab781e913735dc389865a3b8b4a6c6399d/sub-storage/src/lib.rs#L287C17-L287C39).
• Log it all in a nice way (pallet, entry name, entry type, size(s)).

If I'm not missing any steps, this should be fairly easy to do with sub-du as a reference if needed. It hardly needs any Subxt really. This could be a dedicated page on subxt-explorer so that we only run the queries on command, building up output as we go, so I'm game!

[dastansam]

So from a quick look at sub-du and those links I believe that the approach would be:

• Fetch metadata
• Iterate over all storage items in it (https://github.com/paritytech/substrate-debug-kit/blob/e12503ab781e913735dc389865a3b8b4a6c6399d/sub-du/src/main.rs#L190)
• Create a storage key for the root of each storage item and then call the "state_getStorageSize" RPC method (https://github.com/paritytech/substrate-debug-kit/blob/e12503ab781e913735dc389865a3b8b4a6c6399d/sub-storage/src/lib.rs#L287C17-L287C39).
• Log it all in a nice way.

If I'm not missing any steps, this should be fairly easy to do! It hardly needs any Subxt really, and could be a dedicated page on subxt-explorer so that we only run the queries on command, building up output as we go, so I'm game!

I think this is fair assessment.

The only issue is using state_getStorageSize. When I used it in the script it would timeout for almost every relatively large storage entry, f.e System::Account. So I don't think this query can be relied, and it uses broken getPairs and getKeys RPC calls internally. This is why I used state_getKeysPaged to scrape all keys, read the first key's value and multiply number of keys to that value's size (not accurate but fair approximation, I guess).