adroc_thurston
Diamond Member
- Jul 2, 2023
- 7,612
- 10,372
- 106
Safe RPLs clock 5.6 and lower which is slower than N5p.ofc should i announce that N5/4 is worse than Intel 7 cause apparently they can't match the clocks of a wider core ?
Safe RPLs clock 5.6 and lower which is slower than N5p.ofc should i announce that N5/4 is worse than Intel 7 cause apparently they can't match the clocks of a wider core ?
Can we stop talking about nova lake in a Zen 6 thread ?Safe RPLs clock 5.6 and lower which is slower than N5p.
Makes no sense to me. AMD is willing to essentially "delay" Zen 6 a year for N2X instead of just using N2 or N2P? How does that financially make sense? And then Zen 6 is a Razer Lake (or whatever is after NVL) competitor? I don't buy it.I guess I must have been sleeping.
MLID is saying:
1) Zen 6 is on N2X
2) N2X is delayed until 2027 (TSMC slide)
3) Therefore Zen 6 is delayed until 2027
4) AMD will use X3D2 and a refresh of Zen 5 to hold off NVL
So ..... Really? Does everyone else here buy into this?
I guess if I were AMD ..... AND I knew NVL would not supplant a refreshed Zen 5 in performance (excluding MT), perhaps I would keep on N4P and rake in profits waiting on Zen 6 .... but still, that is an insane delay if true.
I'm still betting Venice is released in 2026 (H1) on N2 (not N2P).
If NVL can make a convincing case against a refreshed Zen5 then I would propose that AMD jumped the shark with betting on such an advanced node for desktop.
Is this what you are saying ?I guess I must have been sleeping.
MLID is saying:
1) Zen 6 is on N2X
2) N2X is delayed until 2027 (TSMC slide)
3) Therefore Zen 6 is delayed until 2027
4) AMD will use X3D2 and a refresh of Zen 5 to hold off NVL
So ..... Really? Does everyone else here buy into this?
I guess if I were AMD ..... AND I knew NVL would not supplant a refreshed Zen 5 in performance (excluding MT), perhaps I would keep on N4P and rake in profits waiting on Zen 6 .... but still, that is an insane delay if true.
I'm still betting Venice is released in 2026 (H1) on N2 (not N2P).
If NVL can make a convincing case against a refreshed Zen5 then I would propose that AMD jumped the shark with betting on such an advanced node for desktop.
www.notebookcheck.net
I guess I must have been sleeping.
MLID is saying:
1) Zen 6 is on N2X
2) N2X is delayed until 2027 (TSMC slide)
3) Therefore Zen 6 is delayed until 2027
4) AMD will use X3D2 and a refresh of Zen 5 to hold off NVL
So ..... Really? Does everyone else here buy into this?
I guess if I were AMD ..... AND I knew NVL would not supplant a refreshed Zen 5 in performance (excluding MT), perhaps I would keep on N4P and rake in profits waiting on Zen 6 .... but still, that is an insane delay if true.
I'm still betting Venice is released in 2026 (H1) on N2 (not N2P).
If NVL can make a convincing case against a refreshed Zen5 then I would propose that AMD jumped the shark with betting on such an advanced node for desktop.
Worth separating his leaks from his spin/fictionI guess I must have been sleeping.
MLID is saying:
1) Zen 6 is on N2X
2) N2X is delayed until 2027 (TSMC slide)
3) Therefore Zen 6 is delayed until 2027
4) AMD will use X3D2 and a refresh of Zen 5 to hold off NVL
So ..... Really? Does everyone else here buy into this?
I guess if I were AMD ..... AND I knew NVL would not supplant a refreshed Zen 5 in performance (excluding MT), perhaps I would keep on N4P and rake in profits waiting on Zen 6 .... but still, that is an insane delay if true.
I'm still betting Venice is released in 2026 (H1) on N2 (not N2P).
If NVL can make a convincing case against a refreshed Zen5 then I would propose that AMD jumped the shark with betting on such an advanced node for desktop.
I guess I must have been sleeping.
MLID is saying:
1) Zen 6 is on N2X
2) N2X is delayed until 2027 (TSMC slide)
3) Therefore Zen 6 is delayed until 2027
4) AMD will use X3D2 and a refresh of Zen 5 to hold off NVL
MLID sometimes spins wrong conclusions out of correct info.I guess I must have been sleeping.
MLID is saying:
1) Zen 6 is on N2X
2) N2X is delayed until 2027 (TSMC slide)
3) Therefore Zen 6 is delayed until 2027
4) AMD will use X3D2 and a refresh of Zen 5 to hold off NVL
So ..... Really? Does everyone else here buy into this?
I guess if I were AMD ..... AND I knew NVL would not supplant a refreshed Zen 5 in performance (excluding MT), perhaps I would keep on N4P and rake in profits waiting on Zen 6 .... but still, that is an insane delay if true.
I'm still betting Venice is released in 2026 (H1) on N2 (not N2P).
We're talking about the 32c dense server die being on N2 and the 12C die being on N2P.Isn't the whole point of Zen die reuse? Why would Zen 6 compute dies for desktop and EPYC be on different processes?
Release timeline usually has more to do with prioritizing EPYC volume than anything else.
Indeed AMD has publicly said Venice is coming in 26, everything else we've seen thus far, including mobile and DT, points to 2027. I recall arguing with Adhoc about this, telling him Venice is coming first. That said, I dont expect to see it before July or August at the earliest. If it actually makes H1, its going to be right at the deadline.I guess I must have been sleeping.
MLID is saying:
1) Zen 6 is on N2X
2) N2X is delayed until 2027 (TSMC slide)
3) Therefore Zen 6 is delayed until 2027
4) AMD will use X3D2 and a refresh of Zen 5 to hold off NVL
So ..... Really? Does everyone else here buy into this?
I guess if I were AMD ..... AND I knew NVL would not supplant a refreshed Zen 5 in performance (excluding MT), perhaps I would keep on N4P and rake in profits waiting on Zen 6 .... but still, that is an insane delay if true.
I'm still betting Venice is released in 2026 (H1) on N2 (not N2P).
If NVL can make a convincing case against a refreshed Zen5 then I would propose that AMD jumped the shark with betting on such an advanced node for desktop.
Yes. I think its quite likely if the whole "muh GHz" thing is true. You aint getting world record frequencies on a standard iphone/server class node.
I can understand waiting on N2P only if AMD believes they need it to combat NVL for the next generation (ie, vanilla N2 wouldn't cut it). Just N2P puts Zen 6 desktop off to the end of 2026 to the beginning of 2027. N2X? Now you are off into the ether.We're talking about the 32c dense server die being on N2 and the 12C die being on N2P.
As for the parameter thing, that's not really the same as being on a different process, but it's just my speculation anyway.
They don't 'wait' for anything since neither N2p nor N2x exist for AMD.I can understand waiting on N2P only if AMD believes they need it to combat NVL for the next generation (ie, vanilla N2 wouldn't cut it). Just N2P puts Zen 6 desktop off to the end of 2026 to the beginning of 2027. N2X? Now you are off into the ether.
Indeed. It exploded.On the other hand, AMD did NOT jump on the first gen N3B node.
Can you stop the dementia patient bit? Ze FAD chart says N2 and that's exactly what you're getting.I could still see an AMD Zen 6 desktop/mobile part on N3P. Such a part would likely be more than enough to combat NVL (just as Zen 5 on N4P is more than enough to combat ARL on N3E).
