• 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.

[Canard PC Hardware] Intel prepares Ryzen's response behind the scenes

Page 6 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
Plan B was to soup up 14nm by enhancing it by as much as the rest of the industry is enhancing their 10nm processes compared to their 14nm/16nm processes, tweak the circuit design to allow for higher frequencies without increasing power, and add new media capabilities that have a serious impact on user experience.

In mobile, Kaby Lake is arguably a bigger improvement in CPU perf than either Broadwell or Skylake were. But you seem so set in your belief that Intel sucks that you ignore a lot of this goodness 🙁

dude you can keep defending Intel but just because process improvements happen does not mean architectural improvements cannot be done. AMD moved from Pilderiver (32nm SOI) to Steamroller (28nm SHP bulk) but it also had IPC improvements. This is not unheard of in the fabless ecosystem. Apple keeps improving IPC every year no matter even if there are process improvements. If AMD and Apple can why the heck Intel cannot. This tick tock process optimization rubbish is going to hurt them.
 
dude you can keep defending Intel but just because process improvements happen does not mean architectural improvements cannot be done. AMD moved from Pilderiver (32nm SOI) to Steamroller (28nm SHP bulk) but it also had IPC improvements. This is not unheard of in the fabless ecosystem. Apple keeps improving IPC every year no matter even if there are process improvements. If AMD and Apple can why the heck Intel cannot. This tick tock process optimization rubbish is going to hurt them.

Bristol Ridge???
 
Bristol Ridge???

dude Bristol Ridge is a product which filled a gap in the product roadmap till Raven Ridge arrived. For Raven Ridge both Zen and Vega needed to be done so there was going to be a significant time gap between Carrizo and Raven Ridge. AMD had no interest in any tocks after Excavator as they were busy with Zen. So they did the least they had to do. You forgot about 3 tocks - Piledriver(Trinity) , Steamroller (Kaveri), Excavator (Carrizo) and you picked on the lone Bristol Ridge example. Anyway what about Apple. Any arguments as to why the heck Intel cannot do what Apple can when Intel is supposed to be the world's No.1 semiconductor company.
 
In mobile, Kaby Lake is arguably a bigger improvement in CPU perf than either Broadwell or Skylake were. But you seem so set in your belief that Intel sucks that you ignore a lot of this goodness 🙁
~10% higher clocks with no GPU inprovement. What goodness?
 
I don't know if it's been mentioned but these are socket 2066 hedt chips, Kaby-lake X. Not new, just pulled in a few qtrs to combat ryzen. (if true)
 
remember 10-11 years ago when Intel had a long running arch, NetBurst, and faced fierce competition from AMD on the dual core front? AMD had a more efficient arch and covered most price segments, with a strong back-wind from the success of it's Athlon CPUs vs Inte's P4.

remember what happened then? Conroe happened, and started a decade of market domination.
if AMD pulls off something big with Ryzen, i foresee a Conroe 2.0 towards 2018. the improvements don't have to be architectural, but they SHOULD be.
Intel can't afford to lose now, they've gotten too big.
 
Last edited:
remember 10-11 years ago when Intel had a long running arch, NetBurst, and faced fierce competition from AMD on the dual core front? AMD had a more efficient arch and covered most price segments, with a strong back-wind from the success of it's Athlon CPUs vs Inte's P4.

remember what happened then? Conroe happened, and started a decade of market domination.
if AMD pulls off something big with Ryzen, i foresee a Conroe 2.0 towards 2018. the improvements don't have to be architectural, but they SHOULD be.
Intel can't afford to lose now, they've gotten too big.
Conroe was based on the good know old Pentium M. Netburst was a flop, dead end. Now, there is nothing like this. Intel was very self confident up to this point. They most likely have something really new in development but certainly won't be ready for 2018.
Conroe 2.0 for Intel could be Coffee Lake or Ice Lake, no other options in foreseeable future. But these two options are very readable and doesn't seem like they are going to change a lot.
 
dThis is not unheard of in the fabless ecosystem. Apple keeps improving IPC every year no matter even if there are process improvements. If AMD and Apple can why the heck Intel cannot.
The answer is obvious: Intel IPC already is quite high and their frequency already is quite high. AMD was starting from a sh*tty CPU so gaining a lot of IPC was trivial. Apply isn't targeting >4 GHz (yet) so gaining IPC is easier.

Wake me when either AMD or Apple has the edge on single thread performance over Intel.
 
The answer is obvious: Intel IPC already is quite high and their frequency already is quite high. AMD was starting from a sh*tty CPU so gaining a lot of IPC was trivial. Apply isn't targeting >4 GHz (yet) so gaining IPC is easier.

Wake me when either AMD or Apple has the edge on single thread performance over Intel.
I don't think you will get much sleep.
 
The answer is obvious: Intel IPC already is quite high and their frequency already is quite high. AMD was starting from a sh*tty CPU so gaining a lot of IPC was trivial. Apply isn't targeting >4 GHz (yet) so gaining IPC is easier.

Wake me when either AMD or Apple has the edge on single thread performance over Intel.
 
Followup article by CPCHardware:

https://www.cpchardware.com/core-i7-7740k-et-i5-7640k-kaby-lake-x-lga2066/

They got the i5 7640K sample and it's a LGA2066 but they don't have a compatible MB yet. The CPU advertises itself as LGA1151 via CPUID (tested by sample source). Also, the i5 seems to have no Turbo boost enabled.

They then go on and that Kaby Lake is in fact "just" a Skylake stepping and not a new architecture, same thing for Coffee Lake.

Interesting read it seems to show some kind of disarray at Intel.
 
Followup article by CPCHardware:

https://www.cpchardware.com/core-i7-7740k-et-i5-7640k-kaby-lake-x-lga2066/

They got the i5 7640K sample and it's a LGA2066 but they don't have a compatible MB yet. The CPU advertises itself as LGA1151 via CPUID (tested by sample source). Also, the i5 seems to have no Turbo boost enabled.

They then go on and that Kaby Lake is in fact "just" a Skylake stepping and not a new architecture, same thing for Coffee Lake.

Interesting read it seems to show some kind of disarray at Intel.
It has been known from the start that kaby lake is the exact same core as skylake. Improvements come from a refined process (14nm+).
 
Followup article by CPCHardware:

https://www.cpchardware.com/core-i7-7740k-et-i5-7640k-kaby-lake-x-lga2066/

They got the i5 7640K sample and it's a LGA2066 but they don't have a compatible MB yet.

So to get a 100 MHz boost in clocks (along with a 20W "boost" in power consumption), an entirely new motherboard is required.

Any discernible reason for this? Or is it the usual Intel shenanigans regarding incompatibilities? If it doesn't work on 1151, why the f**k does it not work on 2011?


And to think people used to bitch about Skt939. :-/
 
They got the i5 7640K sample and it's a LGA2066 but they don't have a compatible MB yet. The CPU advertises itself as LGA1151 via CPUID (tested by sample source).
So to get a 100 MHz boost in clocks (along with a 20W "boost" in power consumption), an entirely new motherboard is required.
I'll stick with my prediciton: Intel is scrambling to get SKL-X out ASAP.
 
Carrizo = Bristol Ridge. They're the same thing, only difference is Carrizo uses DDR3 while BR uses DDR4.
There is also a difference in AVFS implementation: http://ieeexplore.ieee.org/document/7417913/ It's paywalled, but in short, Carrizo AVFS gives consensus to a turbo P-state, given by active core numbers, if the current status (temperature etc) is good enough. On Bristol Ridge, the AVFS chooses the maximum P-state attainable, regardless the number of cores active. It is a precursor of current XFR: it's similar, but limited to the max boost supported by the CPU. XFR, AFAIK, is not limited, moreover has 25MHz granularity and it's not bound to p-states...

EDIT: if you know italian, here it is my full post: http://www.hwupgrade.it/forum/showpost.php?p=44459489&postcount=15611
 
There is also a difference in AVFS implementation: http://ieeexplore.ieee.org/document/7417913/ It's paywalled, but in short, Carrizo AVFS gives consensus to a turbo P-state, given by active core numbers, if the current status (temperature etc) is good enough. On Bristol Ridge, the AVFS chooses the maximum P-state attainable, regardless the number of cores active. It is a precursor of current XFR: it's similar, but limited to the max boost supported by the CPU. XFR, AFAIK, is not limited, moreover has 25MHz granularity and it's not bound to p-states...

EDIT: if you know italian, here it is my full post: http://www.hwupgrade.it/forum/showpost.php?p=44459489&postcount=15611

Very interesting. Thanks.

I'm assuming this is accomplished by software/microcode, correct? Or is there a hardware stepping difference too?

About the Italian; technically I don't speak Italian, but I have a good working knowledge of Latin, so I think I got the larger picture... 🙂
 
Back
Top