search

mcmah309 / containeryard

ContainerYard is a declarative, reproducible, and reusable decentralized approach for defining containers.
Apache License 2.0
52 stars 1 forks source link

Enable Link-Time Optimization (LTO) #16

Closed zamazan4ik closed 2 weeks ago

zamazan4ik commented 2 weeks ago

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.

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

I have made quick tests (Fedora 40) by adding lto = true to the Release profile. The yard binary size reduction is from 13 Mib to 11 Mib. Maybe you will also interested in enabling other options like codegen-units, strip, or whatever else.

Thank you.

mcmah309 commented 2 weeks ago

Thanks for this. I added a dist profile, which got the size down to 9.2.