With the release of Alder Lake less than a week away and the "Lakes" thread having turned into a nightmare to navigate I thought it might be a good time to start a discussion thread solely for Alder Lake.
Have you tried changing the power plan to Best Performance?Okay I'm going to admit it. I think Ian was right. The thread director isn't keeping enough compute on Handbrake when I'm transcoding something. For example, right now as I type this it's encoding at 16fps, but when I switch apps and put Handbrake on top it increases to 44fps. Now I could understand keeping Handbrake on the E's if I was doing something that required the P's, like gaming or something, but I'm typing a post in Chrome! No reading to have 8 P's standing at the ready doing nothing.
And yes, I realize I can get this going correctly with process lasso but I shouldn't have to. If you're simply typing in Word or something there is no reason the bulk of the processing power can't go to the background Handbrake encoding automatically. Maybe if there were 16 E's or something this behavior wouldn't be so bad but right now it's kind of dumb.
Of course P-cores consume more power than E-cores, that's why I wrote 2.75-3W on average, because I don't know the exact amount for each core, but let's say your power consumption estimate for each core is correct.Intel has always stated that the E cores were for multithreading and the P cores were power hungry but best at single threading. So, no it is not at all surprising when you take a 125+ W chip, give it only 50 W, have it's P cores suck up the little power you gave it, and you are left with an underperforming chip in a multi-threaded application. At the very least, wait for the non-K versions (especially the mobile or even the T versions) to see how they work at lower powers.
I suspect that at 50 W, the E cores aren't getting 3 W each. At least in the higher power situations, the P cores are taking about 4.5x the power as the little cores. If that ratio stays true when you run down to 50 W, you are looking closer to 5 W each for the P cores and just over 1 W each for the E cores. That might help you get more accurate estimates than assuming 3 W each to all 16 cores.
I found something very interesting.
i9-12900K limited to 50W for both PL1 and PL2 provides only 8872 points in CB R23 and the power consumption is 120W.
If you check Intel Core i9-12900K E-Cores Only Performance Review then you will find out that i9-12900K with only E-cores enabled provides 10366 points in CB R23 and consumes 118W.
You gain ~17% higher score and power consumption is actually 2W lower.
There were several users here who cautioned against taking the results from the latest TPU review at face value.Just E-cores are better than a combination of P+E cores not just in efficiency but also in performance at 50W power limit based on TPU reviews.
Is that really not surprising?
Have you tried changing the power plan to Best Performance?
Well, next year you can get the 13900K.I shouldn't have cheaped out and gone for the 12900K!
Chinese 12400F review. Performance looks good, manages to be faster than stock 5600X.
That's strange. The Anandtech review specifically mentions that the issue with threads being assigned to E cores when the app is not in focus can be addressed in the following three ways:Yes I did. No difference.
- Running dual monitors stops it
- Changing Windows Power Plan from Balanced to High Performance stops it
- There’s an option in the BIOS that, when enabled, means the Scroll Lock can be used to disable/park the E-cores, meaning nothing will be scheduled on them when the Scroll Lock is active.
That's strange. The Anandtech review specifically mentions that the issue with threads being assigned to E cores when the app is not in focus can be addressed in the following three ways:
On Win 10 moving to High Performance doesn't help, and the situation can actually get worse depending on the video encoder you're using. For Handbrake, on default settings (thread priority set to "Bellow Normal"), video encoding may end up on E-core only irrespective on whether the application is on the foreground or not. Handbrake also has settings for thread priority (the same as the ones available through Task Manager).That's strange. The Anandtech review specifically mentions that the issue with threads being assigned to E cores when the app is not in focus can be addressed in the following three ways:
I'm not switching to Win11.Does switching to Win11 fix the problem?
Does switching to Win11 fix the problem?
The same teams of engineers and beta testers who were responsible for the AMD cache latency issues in Windows 11 RTM?It's seems stupid the way it is behaving but I'm sure I'm missing something and I'm the one who is stupid because there is no way that teams of engineers and beta testers who are all magnitudes of order smarter than me could have missed this.
It's clearly a score for the NVIDIA graphics, not the iGPU.LENOVO INVALID - Geekbench
Benchmark results for a LENOVO INVALID with an Intel Core i7-1260P processor.browser.geekbench.com
Core i7 1260P (4+8) Geenbench OpenCL score. This Lenovo laptop includes what might be the mx550 as it has 2 GB of memory (rather stingy IMO).
Not sure how these would look in Win10, but performance seems perfectly fine to me for 1TB Firecuda 530:
My understanding is that the issue affects only certain systems, otherwise it would have been easier to spot in time. I simply don't feel like beta testing for MS, little to win on my side especially considering I need to use this machine for work. I purposely built it and installed the OS on Friday evening so that by Sunday I could decide whether the new machine stays in place or I bring back the old system. I'll reconsider a clean Win11 install at the end of the month. The E-core behavior is weird but it won't affect my workflow.Supposedly it's fixed.
The scheduler behavior is what happens when a major software component development is linked to an arbitrary launch such as Nov 2021 for Alder Lake. It was good enough for review benchmarks, so they shipped. As I said before, I hope Intel puts in serious effort and fixes this for the mobile launch. I plan to disable the E-cores as soon as firmware allows me, but at the same time I also plan to enable them back once team blue figures out how to make E-cores efficient to work with.The Windows 11 Scheduler behavior I don't understand is why when the application that is currently on top is idle or nearly so the rest of the compute doesn't go to background tasks? Or even 80% so the system can feel responsive to the user when they do something during that fraction of a second where the compute resources switch back to the foreground application?
My understanding is that the issue affects only certain systems, otherwise it would have been easier to spot in time. I simply don't feel like beta testing for MS, little to win on my side especially considering I need to use this machine for work. I purposely built it and installed the OS on Friday evening so that by Sunday I could decide whether the new machine stays in place or I bring back the old system. I'll reconsider a clean Win11 install at the end of the month. The E-core behavior is weird but it won't affect my workflow.
Every let's do a clear install every week guy should switch to win 11, they make the maturing process a lot faster. Anyone who either wants to Install windows ONLY when switching computers or major parts (me), or anyone who actually needs to do work on their machine (me at work), should avoid newer windows versions like boiling lava 😂Supposedly it's fixed.
Microsoft Fixes SSD and HDD Write Speed Bug in Windows 11
An issue that's taken Microsoft several months to finally fixwww.tomshardware.com