Hacker News new | past | comments | ask | show | jobs | submit login
Intel Raptor Lake 0x129 CPU Microcode Performance Impact on Linux (phoronix.com)
40 points by dangle1 89 days ago | hide | past | favorite | 9 comments



I have seen a bigger hit on my 13700k on an MSI Z790 board. About 2% on single threaded workloads due to the boost now not going past 5.3Ghz but 20% on multithreaded like Cinebench. The performance hit is really quite significant.

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.


Do you know which BIOS/microcode you were running before updating to 0x129? Multicore workload should never hit anywhere near 1.55V which is the cap from 0x129, and 13700K should be capable of doing 5.4GHz at 1.3V even with the worst bin, so it's a bit strange to see this 20% performance hit on CB.

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).


Perhaps by increasing the power limit to 250W you're also experiencing some thermal throttling now as well if the cooler can't burst fast enough or keep up with that higher wattage.


Its not getting above 75C its being cooled by a 360mm radiator. No thermal throttling at all.


> On a geo mean basis for 188 benchmarks run, the performance overall was flat from this new BIOS / CPU microcode... For the most part the performance was the same but there were some exceptions observed...


Data movement/branch intensive code seems to be affected most (WireGuard -10%, some Python benchmarks -8%).


The branching and the scripting language hit was unexpected. It slows single-threaded programs the most. That means this definitely wasn't caused by an out-of-spec high power limit set on the motherboards. So the common theory was wrong.

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.


>It slows single-threaded programs the most. That means this definitely wasn't caused by an out-of-spec high power limit set on the motherboards. So the common theory was wrong.

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.


Earlier reports believed the motherboard was setting the total power limit too high, like 300W. That would have affected multithreaded workloads.

The voltage spiking during mispredicted vdroop was actually the cause.




Consider applying for YC's W25 batch! Applications are open till Nov 12.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: