perf: enable aggressive release build optimizations#133
Merged
coder3101 merged 2 commits intoMay 16, 2026
Conversation
Contributor
Author
|
If we need to improve the release workflow duration, |
AlexCannonball
force-pushed
the
perf/optimize-release-profile
branch
from
81cd45a to
9863f53
Compare
Owner
definitely, that could be a follow up! |
coder3101
approved these changes
May 16, 2026
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.
Description
Closes #132
This PR optimizes the release profile settings in
Cargo.toml. It introduces Link-Time Optimization (LTO), reduces code generation units to a single core for maximum compiler analysis, and strips heavy debug data while maintaining human-readable panic logs.How Was This Tested?
Tested locally inside the Devcontainer. Verified binary size differences using
ls -lh. Drops from 6.9 MB to 4.7 MB (~32% reduction):cargo build --releasetook ~46 seconds with build optimizations vs. ~18 seconds with no optimizations. I usedcargo cleanbefore each build command.