Last week Intel released an initial set of micro-benchmarks for their oneAPI Level Zero and with L0 support being plumbed into their open-source Intel Compute Runtime, this weekend I started toying around with some Level Zero benchmarks on a variety of Intel processors.

On Friday I posted some initial numbers looking at the LVI mitigation impact when using the LLVM Clang compiler with that open-source, multi-platform compiler having landed its mitigation this week for Intel's Load Value Injection (LVI) vulnerability that was disclosed in March. Through the weekend I have been running some additional tests of this compiler-based mitigation and in this article are some numbers off Cascade Lake Refresh, which while recently released is reported by Intel to still be vulnerable to this new disclosure.

Made public in March was the Load Value Injection (LVI) attack affecting Intel CPUs with SGX capabilities. LVI combines Spectre-style code gadgets with Meltdown-type illegal data flows to bypass existing defenses and allow injecting data into a victim's transient execution. While mitigations on the GNU side quickly landed, the LLVM compiler mitigations were just merged today.

With last week's release of LLVM/Clang 10.0, here are our first benchmarks looking at the stable release of the Clang 10.0 C/C++ compiler compared to its previous (v9.0.1) release on various Intel and AMD processors under Ubuntu Linux.

Following last week's benchmarks of OpenJDK 8 through the newly-released OpenJDK 14 JVM benchmarks, some Phoronix readers expressed interest in seeing Java benchmarks with Oracle's GraalVM as well as Amazon's Corretto JVM implementations. Here are some benchmarks of those benchmarks up against OpenJDK both for Java 8 and Java 11 releases.

Given this week's general availability release of OpenJDK 14, here are some fresh benchmarks looking at all the major releases from OpenJDK 8 through 14 while looking at the JVM performance across multiple workloads.

On Tuesday the Load Value Injection (LVI) attack was disclosed by Intel and security researchers as a new class of transient-execution attacks and could lead to injecting data into a victim program and in turn stealing data, including from within SGX enclaves. While Intel has publicly stated they don't believe the LVI attack to be practical, one of their open-source compiler wizards did go ahead and add mitigation options to the GNU Assembler as part of the GCC toolchain. Here are benchmarks showing the performance impact of enabling those new LVI mitigation options and the significant impact they can cause on run-time performance in real-world workloads.

Following recent discussions about Openwall's Linux Kernel Runtime Guard (LKRG) and the Whonix spin on LKRG for Debian systems and more, here are some benchmarks showing the performance overhead to this run-time integrity checking of the Linux kernel that aims to fend off security vulnerability exploits.

Phoronix Test Suite 9.4-Vestby is now available as one of our largest updates in recent years for our open-source, cross-platform automated benchmarking framework. Almost wanting to rebrand it as Phoronix Test Suite 10, sticking to conventional versioning the Phoronix Test Suite 9.4 release brings numerous result viewer improvements, a lot of polishing to the PDF result exporting, various Microsoft Windows support improvements, new statistics capabilities, some useful new sub-commands, and much more as the latest quarterly feature release.

Given this week's release of Firefox 73 stable that also puts Firefox 74 into beta state, here are fresh Firefox browser benchmarks of Firefox 72/73/74 on Ubuntu Linux with and without WebRender as well as how it compares to the current state of Google Chrome.

Given this week's release of Google Chrome 80, here are fresh benchmarks of Chrome 80 against Firefox 72 on Linux plus also a run with Firefox's WebRender option being enabled. This round of tests was under an Ubuntu 20.04 snapshot with AMD Ryzen processor and AMD Radeon VII graphics.

Last month were benchmarks of RAID benchmarks on four hard drives in not visiting the Linux HDD RAID performance in a while. Stemming from that article were requests of fresh tests of the SSD RAID performance on Linux 5.5 Git, so here are those results for single drive performance and RAID0 / RAID1 / RAID5 / RAID6 / RAID10.

Following the recent AppArmor performance regression in Linux 5.5 (since resolved), some Phoronix readers had requested tests out of curiosity in looking at the performance impact of Fedora's decision to utilize SELinux by default. Here is how the Fedora Workstation 31 performance compares out-of-the-box with SELinux to disabling it.

Last week marked the two year anniversary since the formal public disclosure of the Spectre and Meltdown disclosures. To commemorate that anniversary, I was running some fresh benchmarks of various Intel desktop and server processors with the in-development Ubuntu 20.04 LTS to look at the performance impact today with the default CPU vulnerability mitigations and then again with the mitigations disabled at run-time.

While no major performance improvements were noted as part of the release notes, given this week's Firefox 72 release here are some fresh benchmarks of Firefox 70/71/72 on Ubuntu Linux benchmarked with and without WebRender being enabled. As well, these numbers show how Firefox on Linux is currently stacking up against Google Chrome 79 as its latest stable release.

Stemming from the recent news in Fedora 32 potentially LTO'ing packages by default for better performance and not yet having checked on the Link-Time Optimization performance of the in-development GCC 10, here is a fresh look at the possible performance gains from making use of link-time optimizations for generating faster binaries. This round of testing was done on the AMD Ryzen Threadripper 3960X and is complementary to the recent Profile Guided Optimization benchmarks.

One of the interesting milestones this year in the compiler world was the ability with LLVM Clang 9.0 to compile Linux 5.3+ for x86_64 without needing any extra patches to either the kernel or the LLVM/Clang compiler. That initial support in Linux 5.3 was not without a few issues, but on Linux 5.5 the experience is in great shape with the stable Clang compiler.

Going back to the start of December with the Linux 5.5 merge window we have encountered several significant performance regressions. Over the weeks since we've reproduced the behavior on both Intel and AMD systems along with large and small CPUs. Following some holiday weekend bisecting fun, here is the cause at least partially for the Linux 5.5 slowdowns.

Last week were some benchmarks showing LLVM Clang hitting ~96% the performance of GCC using Intel Ice Lake while now for the recently released Zen2-based AMD Ryzen Threadripper 3960X we are seeing results where overall LLVM Clang is now at performance parity to GCC.

As part of our end-of-year benchmark comparisons, the latest results are looking at how the GNU Compiler Collection has evolved with the past five years of performance in testing GCC 5 through GCC 9 stable and the latest GCC 10 development compiler from the same system.

With 2019 quickly drawing to an end, I figured it would be interesting to see how the performance of Mozilla Firefox has been trending over the longer term. So for this article today is a look at the Firefox 57 through Firefox 71 stable performance plus tests of Firefox 72 beta and Firefox 73 alpha all from the same system and using a variety of browser benchmarks.

Linux 5.5-rc1 is on the way to mirrors and with that the Linux 5.5 merge window is now over. Here is a look at the lengthy set of changes and new features for this next Linux kernel that will debut as stable in early 2020.

Last week marked the release of Blender 2.81 with one of the shiny new features being the OptiX back-end for the Cycles engine to provide hardware-accelerated ray-tracing with NVIDIA RTX graphics processors. Long story short, OptiX is much faster for Blender than using NVIDIA's CUDA back-end -- which already was much faster than the OpenCL support within Blender. For your viewing pleasure today are benchmarks of 19 different graphics cards looking at the CUDA performance from Maxwell to Pascal to Turing and then for the RTX graphics cards also the OptiX performance.

Following the initial tests earlier this month from the disclosures of the JCC Erratum (Jump Conditional Code) that required updated Intel CPU microcode to address and on the same day the TSX Async Abort (TAA) vulnerability that required kernel mitigations to address, which I have run benchmarks of those CPU performance impacts individually, readers have requested tests looking at the current overall impact to the mitigations to date.

For those wondering if it's worthwhile for performance recompiling your key Linux binaries with the microarchitecture instruction set extensions and tuning for Ice Lake, here are some GCC compiler benchmarks looking at that impact for the Core i7 1065G7 on the Dell XPS 7390.

PHP 7.4 is due to be released next week as the annual major iteration to PHP7. Like we have seen through the PHP7 releases, while new features continue to be tacked on for this popular web-based programming language the performance has continued evolving. Here are the latest benchmarks of PHP 5.6 through PHP 7.4 while also looking at the PHP 8.0-dev performance that is in development on Git master.

Using Firefox 70 (including WebRender) and Google Chrome 78, here are our latest round of Linux web browser benchmarks tested on the Dell XPS Ice Lake laptop. Making this round of Linux browser benchmarking more interesting is also including power consumption and RAM usage metrics for the different browser benchmarks.

While this week we have posted a number of benchmarks on the JCC Erratum and its CPU microcode workaround that introduces new possible performance hits, also being announced this week as part of Intel's security disclosures was "Zombieload Variant Two" as the TSX Async Abort vulnerability that received same-day Linux kernel mitigations. I've been benchmarking the TAA mitigations to the Linux kernel since the moment they hit the public Git tree and here are those initial benchmark results on an Intel Cascade Lake server.

With yesterday's overview and benchmarks of Intel's Jump Conditional Code Erratum one of the areas where the performance impact of the updated CPU microcode exceeding Intel's 0~4% guidance was on the web browser performance. Now with more time having passed, here are more web browser benchmarks on both Chrome and Firefox while comparing the new CPU microcode release for the JCC Erratum compared to the previous release. Simply moving to this new CPU microcode does represent a significant hit to the web browser performance.

With the Linux 5.4 kernel set to be released in the next week or two, here is a look at the performance going back to the days of Linux 4.16 from early 2018. At least the Linux kernel continues picking up many new features as due to security mitigations and other factors the kernel performance continues trending lower.