Closed zamazan4ik closed 2 weeks ago
@zamazan4ik thank you very much for letting me know that there is such an build flag LTO, I test it from my macOS M3 and the binary reduces from 3.2MB to 2.4 MB!! I have added it to the release workflow https://github.com/kezhenxu94/ipass/commit/9133f1ee196371a79da7a0338a7ca17a62c48d21
Thanks!!
Hi!
I noticed that in the
Cargo.toml
file Link-Time Optimization (LTO) for the project is not enabled. I suggest switching it on since it will reduce the binary size (always a good thing to have) and will likely improve the application's performance a bit. If you want to read a bit more about LTO, I can recommend starting from this Rustc documentation.I suggest enabling LTO only for the Release builds so as not to sacrifice the developers' experience while working on the project since LTO consumes an additional amount of time to finish the compilation routine. If you think that a regular Release build should not be affected by such a change as well, then I suggest adding an additional
dist
orrelease-lto
profile where in addition to regularrelease
optimizations LTO will also be added. Such a change simplifies life for maintainers and others interested in the project persons who want to build the most performant version of the application. Using ThinLTO should also help to reduce the build-time overhead with LTO. If we enable it on the Cargo profile level, users, who install the application withcargo install
or building the Release Docker image, will get the LTO-optimized version "automatically". E.g., checkcargo-outdated
Release profile.Basically, it can be enabled with the following lines:
I have made quick tests (Fedora 41, Rustc 1.82) by adding
lto = true
to the Release profile. The binary size reduction is from 3.8 Mib to 3.0 Mib.Thank you.