[FEATURE] Evaluate using more advanced compiler optimizations: LTO, PGO, PLO #696
Description
Is your feature request related to a problem? Please describe.
It's not a problem; it's just an idea about how the project's performance can be improved.
Describe the solution you'd like
I noticed that in the Cargo.toml file Link-Time Optimization (LTO) is not enabled. I suggest toggling it on since it will reduce the binary size (always a good thing to have) and will likely improve the application's performance.
I suggest enabling LTO only for the Release builds to not sacrifice the developers' experience during the 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 release-lto profile where additionally to regular release optimizations LTO also will 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.
After applying LTO I can suggest evaluating other optimization options like evaluating Profile-Guided Optimization (PGO) (more materials and benchmarks are available at my repo: https://github.com/zamazan4ik/awesome-pgo) and Post-Link Optimization (PLO) with tools like LLVM BOLT. For these optimizations, I suggest using cargo-pgo.
Describe alternatives you've considered
Leave things as slow as they are for now.
Additional context
Much more information about PGO can be found in my repo: https://github.com/zamazan4ik/awesome-pgo . I would be happy to answer all your questions about PGO and related stuff!
P.S. I left the Issue since Discussions are disabled for the repository. Probably, Discussions' Ideas functionality is a better place to talk about such proposals.