Discussion Intel current and future Lakes & Rapids thread

Page 885 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.

itsmydamnation

Platinum Member
Feb 6, 2011
2,584
2,723
136
No question that it's more MT throughput than needed. Sure rendering, transcoding, and some other tasks will always be able to make use of more cores. But that's getting beyond the 'mainstream' realm which likely wouldn't notice any difference between a 4P+8E configuration and 8P.

Another way to put it. Intel learned their lesson with respect to core counts - it's better to have the 'benchmark wanking' product rather than let the competition run with it.
even one you listed transcoding will prefer a smaller number ( ~8-16) of high performance cores then a sea of lower performance cores ( 16+ )
 
  • Like
Reactions: Thunder 57

SiliconFly

Senior member
Mar 10, 2023
368
213
76
I think that is where we differ. When there are plentiful E cores, there would be no need to preempt the preferred cores. We could finally have dedicated cores to our important programs with no* context switching, no preemption, etc. of those important tasks.


* Yes, gdansk, there would still be context switching of the unimportant tasks on unimportant cores.


"Usually" is not sufficient in my experience. I see all kinds of stutters and delays when background tasks kick in. Maybe it is fine with your tasks. But certainly not for me.
Well, as of now there is no way to avoid context-switching completely. But we can mitigate the effects of context switching by setting process affinity & core pinning.
 

JoeRambo

Golden Member
Jun 13, 2013
1,767
1,989
136
But we can mitigate the effects of context switching by setting process affinity & core pinning.

Only partially. Even on same core if process A ran, then process B ran, once process A needs to run again, it will find TLBs, branch predictors etc etc flushed. Even with caches it's not straitforward due to ASID usage and the common sense fact that B "ran" and evicted lines of A's first run.
It will take a lot of cycles for process A to reach peak perf due to TLBs and BPs needing refilling and 'training".
 

Geddagod

Senior member
Dec 28, 2021
877
695
96
1695142272568.png
Genuinely think Intel borked their slides accidentally, or Intel pulled up like waaaay faster than anyone thought they could. PTL before 2025 sounds wild.
 

JoeRambo

Golden Member
Jun 13, 2013
1,767
1,989
136
Arrow lake is 20A confirmed 😄✅ .. lunar lake is looking good

I am starting to think, that ARL performance estimates were like being Sierra Forrest 144C only -> designed to weed out rabid leakers.
If it is really on 20A, numbers we were "given" don't really make sense at all.

Anyway not long to wait, seems like 2024 is gonna be a year we all will drown in some Lake.
 

H433x0n

Senior member
Mar 15, 2023
474
443
96
I am starting to think, that ARL performance estimates were like being Sierra Forrest 144C only -> designed to weed out rabid leakers.
If it is really on 20A, numbers we were "given" don't really make sense at all.

Anyway not long to wait, seems like 2024 is gonna be a year we all will drown in some Lake.
I hope that’s true but I wouldn’t bet on it. The only way that’s the case is if they can somehow get ARL-S to clock in the neighborhood of 5.4ghz.
 

ASK THE COMMUNITY