You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 little bit. If you want to read more about LTO and its possible modes, I recommend starting from this Rustc documentation.
I think you can enable 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 or release-lto profile where in addition to regular release 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 optimized version of the application. However, if we enable it on the Cargo profile level for the Release profile, users, who install the application with cargo install will get the LTO-optimized version of the game "automatically". E.g., check cargo-outdated Release profile. You also could be interested in other optimization options like codegen-units = 1, etc.
Basically, it can be enabled with the following lines:
[profile.release]
lto = true
I have made quick tests (Fedora 41, Rust 1.82, the latest version of the project) - here are the results for the fake binary:
Release: 5.5 Mib
Release + codegen-units = 1: 3 Mib
Release + LTO: 2.5 Mib
Release + codegen-units = 1 + LTO: 2.3 Mib
Thank you. It would be nice if you would use LTO for your future Rust developments :)
The text was updated successfully, but these errors were encountered:
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 little bit. If you want to read more about LTO and its possible modes, I recommend starting from this Rustc documentation.I think you can enable 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 optimized version of the application. However, if we enable it on the Cargo profile level for the Release profile, users, who install the application withcargo install
will get the LTO-optimized version of the game "automatically". E.g., checkcargo-outdated
Release profile. You also could be interested in other optimization options likecodegen-units = 1
, etc.Basically, it can be enabled with the following lines:
I have made quick tests (Fedora 41, Rust 1.82, the latest version of the project) - here are the results for the
fake
binary:codegen-units = 1
: 3 Mibcodegen-units = 1
+ LTO: 2.3 MibThank you. It would be nice if you would use LTO for your future Rust developments :)
The text was updated successfully, but these errors were encountered: