GCC 10 Link-Time Optimization Benchmarks On AMD Threadripper
Written by Michael Larabel in Software on 7 January 2020. Page 4 of 4. 29 Comments

For most applications, making use of link-time optimizations can help the performance by a few percent.

The PostgreSQL performance improved nicely with LTO optimizations but failed to build on this system with the "-fwhole-program" switch.

SQLite's performance difference was much more minimal.

These results align with our past GCC LTO benchmarks in that making use of link-time optimizations tend to be an easy way to generally squeeze slightly better performance out of large source trees. In some cases the gains can be quite significant as shown in this article. The downside to LTO is greater RAM usage and longer build times, but generally the improved performance of the resulting binary is worthwhile for release builds. Let's hope Fedora and other Linux distributions not yet LTO'ing by default will manage to do so in 2020.

If you enjoyed this article consider joining Phoronix Premium to view this site ad-free, multi-page articles on a single page, and other benefits. PayPal tips are also graciously accepted. Thanks for your support.

Related Articles
About The Author
Author picture

Michael Larabel is the principal author of Phoronix.com and founded the site in 2004 with a focus on enriching the Linux hardware experience. Michael has written more than 20,000 articles covering the state of Linux hardware support, Linux performance, graphics drivers, and other topics. Michael is also the lead developer of the Phoronix Test Suite, Phoromatic, and OpenBenchmarking.org automated benchmarking software. He can be followed via Twitter or contacted via MichaelLarabel.com.

Trending Linux News