• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Discussion Intel current and future Lakes & Rapids thread

Page 856 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
Pretty sure we will never see ADM on any of Intels GT2 SKUs for MTL and ARL. If there is a GT3 for ARL with 320EU or even 384EUs this could be an option. In the older ARL-P roadmap it sounded like ADM will be exclusive to GT3 models to maximize performance (GT3 N3 with ADM to maximize performance). ARL GT2 with 192EUs I don't think we will see this.
 

Intel is going to dynamic thread splitting...
I guess that the Slipstreame 2.0 will come, because E-core is best choice for speculative precomputation.

 

Intel is going to dynamic thread splitting...
I guess that the Slipstreame 2.0 will come, because E-core is best choice for speculative precomputation.
Running speculative thread on E-core would not benefit anything. Speculative thread needs to be run ahead of main thread - so it need to be faster than main thread and so close to main thread that it will be part of cpu core to offer any meaningful help to execution.
 
My bad. I think i didn't explain myself clearly.

(I was just comparing Zen 4 -> Zen 5 vs RPL -> ARL. Thats all)

What I was trying to say was, AMD is going from Zen 4 to Zen 5 (say N4 to N4P), and the density increase is non-existent. So, the transistor budget remains the same. The only way to increase IPC is to re-architect with the same amount of transistors (assuming the die size remains the same).

And Intel is going from RPL to ARL (say Intel 7 to 20A), the density increase is from 100 MTr/mm2 to around 300+ MTr/mm2. ARL gets 3X the transistors for the same die area.

Intel can shrink the ARL die to save cost, but I don't think they'll do that. I think the ARL die is gonna get a significantly higher transistor budget compared to RPL, And those excess transistors can easily be used to increase L2/L3 caches in the cpu tile or even increase core logic for more performance.
At least I was spot on about this a while back... 🙂

I did say ARL is gonna get a bigger cache. News leaks suggest that ARL is getting a 50% bump in L2. i.e, up to 3MB of L2.

Looks like, instead of doing something great with the massive transistor budget, Intel has chosen the easiest & safest way instead. Yuck.
 
Last edited:
Looks like, instead of doing something great with the massive transistor budget, Intel has chosen the easiest & safest way instead. Yuck.
Yeah coz that will mainly translate to better gaming performance and that's what they prefer to focus on. They have been failing at competing in MT workloads for a while now (barely stand up to 5950X and 7950X).
 
I did say ARL is gonna get a bigger cache. News leaks suggest that ARL is getting a 50% bump in L3. i.e, up to 3MB of L3.
Leak was talking about L2 not L3.
Looks like, instead of doing something great with the massive transistor budget, Intel has chosen the easiest & safest way instead. Yuck.
Why can't it be both?
Yeah coz that will mainly translate to better gaming performance and that's what they prefer to focus on.
Eh. Doubt they 'prefer' to focus on gaming performance.
They have been failing at competing in MT workloads for a while now (barely stand up to 5950X and 7950X).
?
 
Why can't it be both?
I don't think it can be. Some leaks suggest ARL has RWC+ cores. Others suggest it has the first iteration of the LNC cores (and hence no hyper-threading).

If ARL has RWC+ cores, then there's nothing new to expect, except bigger caches and some minor improvements I guess.

If it has some form of LNC, then it's a whole different story. Need more clarity about ARL cores though.
 

View attachment 84509
Even their KS paired with faster memory has trouble matching a 7950X in overall MT perf.
The benchmark you linked shows a single percentage point difference. I wouldn't consider that having trouble matching 7950X MT performance.

Just to save us time... Yes - I know it isn't anywhere near as efficient.
 
Isn't he the hardcore intel apologist? can someone explain rentable cores to me.
From what I understand, Intel will slice a single thread into different instruction streams and try to process them on different cores so that if one instruction stream comes to a halt for whatever reason, the processing keeps going on, on the other cores and results are ready before the execution reaches that part of the process's instructions.
 
From what I understand, Intel will slice a single thread into different instruction streams and try to process them on different cores so that if one instruction stream comes to a halt for whatever reason, the processing keeps going on, on the other cores and results are ready before the execution reaches that part of the process's instructions.
That makes sense on paper but I'm not sure that's how it works in real life. I'm just an arm chair CPU architect, but if a single thread could be simply chopped up into smaller, bite sized portions that can be executed in parallel, wouldn't a GPU be better at the task? Single threaded processes tend to have a crap load of dependencies, which is why they run best on CPUs to begin with. If portions of the instruction stream could be done in parallel, well that's where having a superscaler execution engine comes in.
 
That makes sense on paper but I'm not sure that's how it works in real life. I'm just an arm chair CPU architect, but if a single thread could be simply chopped up into smaller, bite sized portions that can be executed in parallel, wouldn't a GPU be better at the task?
You would need a GPU that understood x86, AKA LARRABEE! 😀
 
From what I understand, Intel will slice a single thread into different instruction streams and try to process them on different cores so that if one instruction stream comes to a halt for whatever reason, the processing keeps going on, on the other cores and results are ready before the execution reaches that part of the process's instructions.

Isnt it what a OoO uarch is supposed to do..?.
 
From what I understand, Intel will slice a single thread into different instruction streams and try to process them on different cores so that if one instruction stream comes to a halt for whatever reason, the processing keeps going on, on the other cores and results are ready before the execution reaches that part of the process's instructions.
very similar to how download streams work. each connection within the main download will download a portion of the file, if one fails others take over and then decompress the download from cache.

this being intel and I need not explain some half baked ideas they've had. I'm not sure if it'll work out well or bad.
 
Back
Top