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 due to more aggressive compiler optimizations. If you want to read more about LTO and its possible modes, I recommend starting from [this](https://doc.rust-lang.org/rustc/codegen-options/index.html#lto) 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. In this case, we can create a dedicated `[profile.optimized-dev]` profile where LTO will be disabled (so developers experience will not be affected). 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 app "automatically". Additionally, GitHub Releases' binaries will also be automatically optimized with LTO during release routines. E.g., check `cargo-outdated` Release [profile](https://github.com/kbknapp/cargo-outdated/blob/master/Cargo.toml#L48). You also could be interested in other optimization options like `codegen-units = 1` - it also brings improvements over the current defaults. Basically, it can be enabled with the following lines to the root Cargo.toml file: ``` [profile.release] codegen-units = 1 lto = true ``` I have made quick tests (Macbook M1 Pro, Rust 1.86, the latest version of the project at the moment, `cargo build --release` command) - here are the results: * Release: 10 Mib, clean build time: 38s * Release + `codegen-units = 1` + Fat LTO: 7.3 Mib, clean build time: 1m 24s Thank you.
This issue appears to be discussing a feature request or bug report related to the repository. Based on the content, it seems to be still under discussion. The issue was opened by zamazan4ik and has received 0 comments.