Intel Raptor Lake 0x129 CPU Microcode Performance Impact on Linux
phoronix.com
phoronix.com
Its made even worse by the fact the pre microcode benchmark was on a hand application of Intels Default power recommendations to reduce damage, so 125W and limitations on amps and boost times. Its now running on performance mode which can use 250W. I don't understand how some people see no difference, others seeing a little and I am seeing a lot. Something is going on here.
If this is compared to <= 0x123 (before the introduction of "Intel Default Settings") then this drop may be attributed to low AC Load Line configuration in previous configuration, which essentially undervolting the CPU out-of-the-box. >= 0x125 BIOS usually bumped this up/lower this down to Intel's recommendation. It could be very possible that AC_LL is setting too high on the MSI board after the fix.
It's still very strange though, even if AC_LL is the culprit, that 253W is running 20% slower than 125W. For what it's worth, I have two systems running 13900K and 13700K both with ASRock board, and I see no difference in MT performance with 1-2% drop in ST (though 13700K is running with PL1=PL2=125W, but that shouldn't affect ST).
Games seem to be unaffected. There was suspicion regarding the timing of this patch and AMD's new processors coming out. That now seems to be unfounded, with only a minimal effect on consumer applications.
No, low thread workloads draw more volts than high thread workloads. This is easily observable using anything that measures CPU voltages. Single threaded use cases seeing more impact, if any, is completely within expectations.
That said, Intel said performance drops should be negligible if any.
I haven't updated my system yet since ASUS's releases are currently marked as beta, but I don't expect there to be notable performance drops either. Granted, my 14700K in my daily driver has been working perfectly fine since I bought it and so have all the other Raptor Lake machines I care for.
The voltage spiking during mispredicted vdroop was actually the cause.