The 3.30 certainly performs much better than the test version, perhaps the issue was discovered and a last minute fix was applied before release.
In relation to SEV, my kernel config on Gentoo has the following disabled:
CRYPTO_DEV_SP_PSP Platform Security Processor (PSP) device
CRYPTO_DEV_CCP Support for AMD Secure Processor
CRYPTO_DEV_CCP_DD Secure Processor device driver
CONFIG_KVM_AMD_SEV AMD Secure Encrypted Virtualization (SEV) support
I ran through the benchmark with “top | grep systemd” running in another terminal and systemd’s %CPU usage remained 0.0
I don’t know what Fedora has set in the kernel, but will check systemd’s usage and update this post.
UPDATE: systemd %CPU usage on Fedora as well.
The MBW 128 MiB test seemed to drop right back in line with your original slower results, is this repeatable? If it flips between fast and slow that’s something to note. The other results give the impression that some default memory timing may have changed between the two BIOS’s.
The “Stream” test results seem overly sensitive to minor changes, and often, tweaks that improve it’s results are detrimental to other tests, where the results take a hit.
“Ramspeed” runs the same sort of tests (copy, triad, scale, add, average), and the effect of tuning can be quite different to that of “Stream”.
The ramspeed file auto-downloaded from Phoronix was broken when I installed the test, I’ll presume it still is. I downloaded the source via the Arch repository (link pulls from buildroot.net) and placed it in phoronix’s download cache directory and this works fine.
In my case, the phoronix cache dir is “/var/cache/phoronix-test-suite/download-cache/”.
File on buildroot:
The following command runs the bench:
phoronix-test-suite benchmark ramspeed
It’s probably a good idea to throw in a few memory intensive “real workload” tests to see if/how these are being affected. Media encoding/decoding and file compression/decompression tests could be good candidates.
In theory, re-seating the RAM could improve a previously higher resistance connection (dust perhaps) which could change auto training results, though it’s a low probability.
I ran a fresh benchmark from Fedora with your ASRock timings applied and it’s quite a good match with your “2990WX + GSkill 2933 128gb DFL 3.33A Agesa 220.127.116.11” scores.