remote-externalities: 'instant' snapshots, threading refactor, better progress logs#14057
remote-externalities: 'instant' snapshots, threading refactor, better progress logs#14057liamaharon merged 21 commits intomasterfrom
Conversation
…mote-externalities-refactor
|
Converting this to a draft, I'd like to include a switch to inserting keys directly into |
|
Tested it for all four parity nodes and it works with this patch, thanks! |
kianenigma
left a comment
There was a problem hiding this comment.
It looks very promising!
I think now's a good time to revisit https://github.com/paritytech/devops/issues/2083 and its importance as well.
With the end goal of making this usable (in a stable and fast way 🙈) in our CI, it would make a lot of sense to have snapshots ready in our infra, and have the CI use those. With this fast loading time, it would be a smooth process.
It is pretty fast now. Takes about 3 minutes locally and 15 in CI. |
ggwpez
left a comment
There was a problem hiding this comment.
Looks pretty good, thanks!
What is this file utils/frame/remote-externalities/test_data/proxy_test?
…mote-externalities-refactor
|
@ggwpez |
…ress logs (#14057) * remote externalities refactor * remove redundant logs * use const for parallel requests * prefer functional * improve variable naming * handle requests error * use overlayedchanges * Revert "use overlayedchanges" This reverts commit c0ddb87. * Revert "Revert "use overlayedchanges"" This reverts commit 1d49362. * Revert "Revert "Revert "use overlayedchanges""" This reverts commit 06df786. * backup/load raw storage values * test raw storage drain and restore * update snapshot tests * improve logs * clippy suggestions * address comments * fix example * fix test * clippy
…ress logs (#14057) * remote externalities refactor * remove redundant logs * use const for parallel requests * prefer functional * improve variable naming * handle requests error * use overlayedchanges * Revert "use overlayedchanges" This reverts commit c0ddb87. * Revert "Revert "use overlayedchanges"" This reverts commit 1d49362. * Revert "Revert "Revert "use overlayedchanges""" This reverts commit 06df786. * backup/load raw storage values * test raw storage drain and restore * update snapshot tests * improve logs * clippy suggestions * address comments * fix example * fix test * clippy
…ress logs (paritytech#14057) * remote externalities refactor * remove redundant logs * use const for parallel requests * prefer functional * improve variable naming * handle requests error * use overlayedchanges * Revert "use overlayedchanges" This reverts commit c0ddb87. * Revert "Revert "use overlayedchanges"" This reverts commit 1d49362. * Revert "Revert "Revert "use overlayedchanges""" This reverts commit 06df786. * backup/load raw storage values * test raw storage drain and restore * update snapshot tests * improve logs * clippy suggestions * address comments * fix example * fix test * clippy
…ress logs (paritytech#14057) * remote externalities refactor * remove redundant logs * use const for parallel requests * prefer functional * improve variable naming * handle requests error * use overlayedchanges * Revert "use overlayedchanges" This reverts commit c0ddb87. * Revert "Revert "use overlayedchanges"" This reverts commit 1d49362. * Revert "Revert "Revert "use overlayedchanges""" This reverts commit 06df786. * backup/load raw storage values * test raw storage drain and restore * update snapshot tests * improve logs * clippy suggestions * address comments * fix example * fix test * clippy
Instant(ish) snapshot loading
Snapshot load performance (Macbook Pro M2 Max)
Removes threading
try-runtime-clipanics on Polkadot #14006Better progress logs
Kusama
on_runtime_upgradelivelogsScreen.Recording.2023-05-03.at.12.11.20.mp4
TODO Check pulling data from these remotes works:
wss://polkadot-try-runtime-node.parity-chains.parity.io:443wss://kusama-try-runtime-node.parity-chains.parity.io:443wss://westend-try-runtime-node.parity-chains.parity.io:443