Wasm size optimization round 2 (post-feature target 30% reduction)#81
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! 🚀 |
|
Done, Close: #81 |
|
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. |
done |
|
Clean merge. Round-2 Wasm size optimization (Cargo.toml tweaks + SIZE.md writeup + CI workflow). Thanks @OluRemiFour. |
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.