- Oct 9, 1999
- 5,109
- 3,635
- 136
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.
Yeah that was a mess. Kinda makes you wonder why they continued with heterogeneous core configs in a flagship product after that particular disaster.
Golden Cove>> Sunny Cove/Rocket Lake, they would never dare to release Lakefield type of performance on the desktop
Thax for posting , kind of matches what we all know/have seen in other reviews , its not a bad uarch, its just not amazing and get's the performance it has by being bigger not smarter.Popping the Hood on Golden Cove
Alder Lake (ADL) is the most exciting Intel launch in more than half a decade.chipsandcheese.com
Some incredible info and comparisons inside. These guys (girls?) really picked up a torch of proper architectural investigation. A highly recommended read!
Thax for posting , kind of matches what we all know/have seen in other reviews , its not a bad uarch, its just not amazing and get's the performance it has by being bigger not smarter.
And I don't get DrMrLordX's assertion that hetero core configs are crap
Well all the benchmarks are completely dumb compute jobs so there is zero wiggle room for smarter doing anything.Thax for posting , kind of matches what we all know/have seen in other reviews , its not a bad uarch, its just not amazing and get's the performance it has by being bigger not smarter.
Just saying that a Desktop Sunny Cove/Tremont hybrid would not cut it for for desktop against Amd Current and up coming Desktop CPUs, they had to push Alderlake(the 12900K) to match a stock 5950X(When the 5950X is without limits the story changes). Do you thing a 8C/16T Sonny cove + 8C/8T Tremont Hybrid would keep up?Nicalandia are you saying Sunny Cove was crap?
Well all the benchmarks are completely dumb compute jobs so there is zero wiggle room for smarter doing anything.
Nobody benches the new scheduler because that would be extremely hard to do, nobody benches avx 512 instead only uses it to highlight power peaks, nobody gives quicksync or iGPU AI the time of day.
At the end of the day if all that reviews focus on is dumb compute then that's the type of CPUs we will get.
That would defeat the purpose of e-cores, to save on space and powerI wonder if they are going to squeeze AVX512 into to future E-Cores.
4K gaming doesn't need P-cores. A new BIOS option needed to disable P-cores with a keypress to save power in such a scenario.
Doom Eternal LOVES E-cores
To save what, 10 Watts in a gaming system that will already be using 400W+?View attachment 53762
4K gaming doesn't need P-cores. A new BIOS option needed to disable P-cores with a keypress to save power in such a scenario.
Those values are not gaming ones, they would be even lower there. He uses CB R23.To save what, 10 Watts in a gaming system that will already be using 400W+?
View attachment 53765
If you want to save power in a 4K gaming system you simply downclock your CPU. No need to reinvent the wheel.
Intel Core i9-12900K E-Cores Only Performance Review
With Alder Lake, Intel is betting big on hybrid CPU core configurations. The Core i9-12900K has eight P(erformance) cores and eight E(fficient) cores. We were curious and tested the processor running the E-Cores only to see how well they perform against architectures like Zen 2, Zen 3, Skylake...www.techpowerup.com
View attachment 53760
MySQL hates the E-cores.
View attachment 53761
Doom Eternal LOVES E-cores
View attachment 53762
4K gaming doesn't need P-cores. A new BIOS option needed to disable P-cores with a keypress to save power in such a scenario.
I know, that was the point: if 8 P cores @ 3.9Ghz with HT disabled use just 22W more than 8 E-cores under Cinebench (while offering 20% higher score), then gaming power delta is bound to be significantly less. In fact, if we were to aim for ISO performance, there's a very good chance the P-cores would end up using less power than the E-cores.Those values are not gaming ones, they would be even lower there. He uses CB R23.
You could try a Virtual Machine and have it used only the P Cores, do the same for E cores and compare it, Process Lasso is obviously not the best since the P cores are taking care of other task the OS is doing while the e cores are being testedSeeing how the primary purpose of Gracemont is MT performance in as little area as possible I still think adding HT w
Having examined many of these "E cores" only tests and tested my 12700K I won't have much trust in their validity. The fact that the P's can't be completely disabled means Process Lasso or some other software means must be used to try and isolate the E's and they are slippery as the P's always seem to sneak into the action.
Some examples. The E only Handbrake score in the Anandtech bench doesn't make sense. 87fps for the HVEC Handbrake test is clearly not correct.
Cinebench R23 E tests show results that when you add P and E separate results the combined total is much higher than when both are run concurrently. Either the P's are taking care of all background tasks, inflating the E score, or helping with the test, also helping the score.
At this point in time I like E core isolated scores that are obtained by subtracting P scores from the P+E scores. The E cores can be shut down in the BIOS so I have some trust in P only scores. Also an imperfect way to evaluate E cores but I think better than the affinity solution.
Also the elephant in the room is why Intel won't allow the E to "run the show" by themselves? Is there some tasks the P's must perform?
Anyway from testing on my 12700K I have some faith in the following.
P core at 4.7GHz with HT scores 2355. E cores score 973 in ST test at 3.8GHz and 909 subtracting P from P+E result, E's at 3.6 of course.
So, in CB R23 P's do 501 point per GHz while E's do 254 points per GHz.
P cores are 98.6% faster than E's in CB R23, or almost twice as fast. This means that at 4.7/3.6GHz and assuming P and 4E cluster requires the same die space the E's are 1.54 times more productive for the die area they consume.
And that of course is the reason for their existence.
Also I believe that the superwide design of the Gracemont cores is directly related to their "tuning" for MT performance. We have 6 decoders in 2x3 clusters and if I remember correctly 17 decode. But, the OoS is much more primitive than Golden Cove, meaning MT throughput will only be high if the incoming code is already highly parallel as Gracemont doesn't the smarts to work it out on the fly.
Those using Processlasso make sure you are on the latest version as it adds support for Alder-lake and also has CPUsets, though I don't know if that would change outcome of your tests.You could try a Virtual Machine and have it used only the P Cores, do the same for E cores and compare it, Process Lasso is obviously not the best since the P cores are taking care of other task the OS is doing while the e cores are being tested
Edit.
I would like to add that Virtual Machines can be use to test the strength or weakness of a particular CPU design, for example on Zen/Zen+ there was big penalties from apps jumping thru cpu chiplets. to test this you could design a Virtual Computer and assign core in the worst possible way. One could also do the same with Alderlake.
A virtual Machine is a better way to test since the P cores will not allow the OS to crash if the E CPUs are 100% stressed. in a Virtual Machine the OS on the virtual hardware can't have access to the P coresThose using Processlasso make sure you are on the latest version as it adds support for Alder-lake and also has CPUsets, though I don't know if that would change outcome of your tests.
On my end with 12600k I get with E cores only CM-r15 602 and 1834 with just P cores. though it takes a few seconds for all P cores to load to 100% so should be higher..
All 10 cores it gets 2589
I forgot to mention, I have VMware player but it isn't working right as far as the core count setting that it uses. I think it needs a update for alder lake.A virtual Machine is a better way to test since the P cores will not allow the OS to crash if the E CPUs are 100% stressed. in a Virtual Machine the OS on the virtual hardware can't have access to the P cores
nobody benches avx 512