Benchmarking The Performance Impact To AMD Inception Mitigations

Written by Michael Larabel in Software on 15 August 2023 at 10:30 AM EDT. Page 3 of 8. 35 Comments.

DaCapo Benchmark benchmark with settings of Java Test: Jython. safe RET no microcode was the fastest.

DaCapo Benchmark benchmark with settings of Java Test: Tradebeans. off was the fastest.

For the DaCapo OpenJDK Java benchmarks there was a performance impact namely where using the alternative IBPB mode.

The safe RET mitigation did impact the 7-Zip compression benchmark performance.

Timed Godot Game Engine Compilation benchmark with settings of Time To Compile. off was the fastest.

Timed Linux Kernel Compilation benchmark with settings of Build: defconfig. off was the fastest.

Timed Linux Kernel Compilation benchmark with settings of Build: allmodconfig. off was the fastest.

Timed LLVM Compilation benchmark with settings of Build System: Ninja. off was the fastest.

Timed Node.js Compilation benchmark with settings of Time To Compile. off was the fastest.

One of the real-world areas where the AMD Inception mitigations did hurt the performance was in code compilation speed. The EPYC 7763 server was showing various open-source projects taking a few seconds longer to build now with the safe RET mitigations. Interestingly the new CPU microcode didn't provide much of a difference over the pure kernel-only mitigation run. The alternative IBPB mitigation showed the worst performance penalties.

35 Comments - Next Page

Page: 1 2 3 4 5 6 7 8 Next Page