Wasm size optimization round 2 (post-feature target 30% reduction)#81
Open
OluRemiFour wants to merge 1 commit into
Open
Wasm size optimization round 2 (post-feature target 30% reduction)#81OluRemiFour wants to merge 1 commit into
OluRemiFour wants to merge 1 commit into
Conversation
|
@OluRemiFour Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
Author
|
Done, Close: #81 |
Contributor
|
Just one conflict in git fetch origin
git rebase origin/develop
git push --force-with-leaseKeep develop's existing CI jobs plus your size-budget job alongside them. SIZE.md and Cargo.toml profile additions land cleanly. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Close: #49
The WASM size optimization task is complete!
Since the original stellar/SIZE.md couldn't be found, we established a new "before" baseline from the current standard release build, which ranged up to ~115 KB per contract.
With the optimization tweaks added directly into the Cargo.toml [profile.release] configuration (leveraging size-optimization, link-time optimization, and symbol stripping), we reduced all contracts dramatically. They now weigh under 10 KB each (for instance, the heavy wraith_names.wasm dropped from 115.21 KB down to just 9.53 KB)!
Furthermore, the CI gate logic has been fully implemented into your .github/workflows/ci.yml pipeline. It checks each compiled *.wasm file and strictly fails if any payload exceeds 112,640 bytes (110 KB). A new stellar/SIZE.md documentation has also been assembled containing your troubleshooting recipe.