-
Notifications
You must be signed in to change notification settings - Fork 138
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
Optimize storage migration: Allow skipping of values #3157
Conversation
Cadence Benchstat comparisonThis branch with compared with the base branch onflow:master commit 13610ac Collapsed results for better readability
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #3157 +/- ##
==========================================
+ Coverage 80.54% 80.61% +0.06%
==========================================
Files 381 381
Lines 92764 92890 +126
==========================================
+ Hits 74717 74879 +162
+ Misses 15337 15304 -33
+ Partials 2710 2707 -3
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice optimization
Work towards #3096
Description
Optimize the Cadence 1.0 migration by allow value migrations of a storage migration to indicate that they do not need to migrate a certain value. Skip the migration of a (potentially nested) value, if all value migrations agree.
Implement skipping for all value migrations.
For example, this will heavily reduce the migration time for accounts which store lots of "binary data" in
[UInt8]
, and nested variants (e.g.[[UInt8]]
).master
branchFiles changed
in the Github PR explorer