The Firefox + Chrome Web Browser Performance Impact From Intel's JCC Erratum Microcode Update
Written by Michael Larabel in Software on 13 November 2019. Page 3 of 3. 21 Comments

Next was Google Chrome 78 as the latest stable release.

The Chrome performance was even more profoundly impacted by the new Intel microcode for mitigating the Jump Conditional Code Erratum. The most extreme outlier was Basemark being 21% faster on the older code but JetStream, Octane, and ARES-6 were all above 4% faster when using the previous microcode revision.

If taking the geometric mean of all these web bowser benchmarks from Firefox and Chrome, the new microcode led to an average of 4.2% lower performance from yesterday's MCU. That's just looking at the microcode update pertaining to JCC Erratum while -- separately -- Zombieload TAA tests are also being worked on for publishing soon.

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