You know how ISPs used to sell "up to X Mbps"? Same idea. Your chip will turbo boost "up to 6.00 GHz".
It's basically automated overclocking, and as you learned, sometimes it can't even do it in a stable fashion. Some of those chips will never clock "up to 6.00 GHz" but they didn't lie. "up to"
And laptops have another layer of bullshit, because the theoretical boost clocks the chip is capable of will in practice be limited by the power delivery and cooling provided by that specific machine, and the OEMs never tell you what those limits are. So they'll happily take an extra $200 for another 100MHz that you'll never see for more than a few milliseconds while a different model with a slower-on-paper CPU with better cooling can easily be more than 20% faster.
Its hard to cool these new chips. AMD included.
So unless you have powerful cooling you will hit the thermal limit.
enable settings that capped max watts and temperature for throttling to 90c.
You were going above 90C before???My first thought is that seems insane, but is apparently normal for that chip, according to Intel: "your processor supports up to 100°C and any temperatures below it are normal and expected"
https://community.intel.com/t5/Processors/i9-14900K-temperat...
That is just wild though. On one hand you should obviously get the performance that was advertised and that you paid for. On the other hand IMO operating a CPU at 90-100C is just insane. It really feels like utter desperation on Intel's part.
I would be curious what kind of cooling setup you have.
No it isn't, the manufacturer literally says it's normal! I think people who spend as much money on cooling setups as the chip are the insane ones.
My favorite story: I once put Linux on a big machine that had been running windows, and discovered dmesg was full of thermal throttling alerts. Turns out, the heatsink was not in contact with the CPU die because it had a nub that needed to occupy the same space as a little capacitor.
I'd been using that machine to play X-plane for over two years, and I never noticed. It was not meaningfully slower: the throttling events would only happen every ten or so seconds. I'm still using it today, although with the heatsink fixed :)
I have a garage machine with a ca. 2014 Haswell that's been running full tilt at 90C+ for a good bit of its life. It just won't die.
I have a garage machine with a ca. 2014 Haswell
that's been running full tilt at 90C+ for a good
bit of its life. It just won't die.
First of all: that's awesome.Second: what's it doing spending that much time "full-tilt?" Just curious. Sounds like something interesting.
Right now, I use it as a 200W space heater I can turn off and on via SSH, just running busyloops. It works well enough for a single car garage in California.
First, the temperature sensors got a lot better. Previously you only had one sensor per core/cpu, and it was placed wherever there was space - nowadays it'll have dozens of sensors placed in the most likely hotspots. A decade ago a 70C temp meant that some parts of the CPU were closer to 90C, whereas nowadays a 90C temp means the hottest part is actually 90C.
Second, the better sensors allow more accurate tuning. While 100C might be totally fine, 120C is probably already going to cause serious damage. The problem here is that you can't just rely on a somewhat-distant sensor to always be a constant 20C below the peak value: it's also going to be lagging a bit. It might take a tenth of a second for that temp spike in the hotspot to reach the sensor, but in the time between the spike starting and the temp at the sensor raising enough to trigger a downthrottle you could've already caused serious damage. A decade ago that meant leaving some margin for safety, but these days they can just keep going right up to the limit.
It's also why overclocking simply isn't really a "thing" anymore. Previous CPUs had plenty of safety margin left for risk-takers to exploit, modern CPUs use up all that margin by automatically overclocking until it hits either a temperature limit or a power draw limit.
Similarly, processors convert thermal headroom to performance, until they run out of thermal headroom. So if you improve the cooling on a processor that has work to do (rather than sleeping), it will use up that cooling and perform better, rather than performing the same and running cooler.
(Mobile processors operate differently, since they need to maintain a much tighter thermal envelope to not burn the user. And processors can also target power levels rather than thermals. But when a processor is in its default "run as fast as possible" mode, its normal operating temperature will be close to the 100C limit.)
This is really no excuse to have Windows eating 12GB of RAM with an Edge (with 2 static tabs), excel some antivirus and Teams running. This (12GB) is just sick.
If you have free ram the OS will cache all the recently accessed things. It costs effectively zero to cache them when you access them, and it costs effectively zero to evict from the cache if you actually need the memory for "useful" work. And if the cached thing is useful in the mean time, you win because RAM is still orders of magnitude faster than SSD. None of the scenarios are a perf loss. The only scenarios are "win" or "no gain."
"But won't the next application I load, load faster if there is free RAM?"
If you are asking this question, please refer back to the previous concept -- "it costs effectively zero to evict from the cache if you actually need the memory for 'useful' work." This is where people typically get confused. They think it takes work to evict things from the cache, just like it would require work to remove frequently used objects from your physical desk if you needed to free up space.
Once you understand that the rest should fall into place.
Unless you take reliability into account.
It might look insane compared to what you were used
to seeing a decade ago, but it's actually not that crazy.
I'm comparing it to a mid-range system I built last year: an Intel i5-13400F with a $60 closed-loop cooler.It doesn't go past 45C even during Prime95 runs using all cores. And the 120mm fans aren't exactly howling either.
First, the temperature sensors got a lot better. Previously
you only had one sensor per core/cpu, and it was placed wherever
there was space - nowadays it'll have dozens of sensors placed
in the most likely hotspots.
That's awesome to know. Thanks for the explanation.How much margin is really there?
Therefore, 1.1x the frequency at the high end (where switching power dominates) is 1.33x the power draw.
Those final few hundred MHz really hurt. Conversely, that's also why you see "Eco" power profiles with a major reduction in power draw that cost you maybe 5-10% of your peak performance.
I'm curious about what you are using for cooling, as 90C at 5.4ghz seems way off compared to what I am seeing on my processor, but it could just be that I'm not pushing my processor quite as hard even with the higher clock rate.
It was a nightmare to get running stable. None is the default settings the motherboard used worked. Games crashed, kernel and emacs compiles failed.
End result I had to cap turbo to 5.4ghz on a 6ghz chip, and enable settings that capped max watts and temperature for throttling to 90c.
System seems stable now. Can get sustained 5.4ghz without throttling and enjoying games at 120fps with 4k resolution.
Even though it is working I do feel a way about not being able to run the system at any of the advertised numbers I paid for.