[GH-ISSUE #569] Enable Link-Time Optimization (LTO) #328

New issue

Open

opened 2026-03-02 23:46:36 +03:00 by kerem · 0 comments

kerem commented

2026-03-02 23:46:36 +03:00

Owner

Originally created by @zamazan4ik on GitHub (Oct 8, 2024).
Original GitHub issue: https://github.com/aome510/spotify-player/issues/569

Is your feature already implemented in the latest master?
No

Is your feature request related to a problem? Please describe.
It's not a problem - just an improvement idea

Describe the solution you'd like
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. At least one person also tried to enable LTO in their builds.

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 or release-lto profile where additionally 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 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 with cargo install, will get the LTO-optimized version "automatically". E.g., check cargo-outdated Release profile.

Basically, it can be enabled with the following lines:

[profile.release]
lto = true

Describe alternatives you've considered
Leave things as is

Additional context
N/A

Originally created by @zamazan4ik on GitHub (Oct 8, 2024). Original GitHub issue: https://github.com/aome510/spotify-player/issues/569 **Is your feature already implemented in the latest `master`?** No **Is your feature request related to a problem? Please describe.** It's not a problem - just an improvement idea **Describe the solution you'd like** 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. At least one person also [tried](https://github.com/aome510/spotify-player/issues/149#issue-1602209595) to enable LTO in their builds. 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` or `release-lto` profile where additionally 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 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 with `cargo install`, will get the LTO-optimized version "automatically". E.g., check `cargo-outdated` Release [profile](https://github.com/kbknapp/cargo-outdated/blob/master/Cargo.toml#L48). Basically, it can be enabled with the following lines: ``` [profile.release] lto = true ``` **Describe alternatives you've considered** Leave things as is **Additional context** N/A