What's Intel's roadmap going forward?

[Mockingbird]

As the title said: What's Intel's roadmap going forward?

Nehalem => Westmere => Sandy Bridge => Ivy Bridge => Haswell => Broadwell => Skylake => Kaby Lake => Coffee Lake

Could someone help filled in the rest with the following?

Whiskey Lake

Amber Lake

Comet Lake

Cannon Lake

Ice Lake

Tiger Lake

Alder Lake

Meteor Lake

 

[.vodka]

Wikichip's progression says:

Coffeelake/Cannonlake -> Ice Lake -> Tiger Lake / Sapphire Rapids -> Alder Lake -> Meteor Lake
Whiskey Lake
Amber Lake

Spoiler: Wikipedia's:

Supposedly:

Whiskey/Amber Lake:

Whiskey Lake (WHL) is a microarchitecture designed by Intel as a successor to Kaby Lake for ultra-low power mobile devices, launched concurrently with Coffee Lake and Amber Lake.

Amber Lake is a microarchitecture designed by Intel as a successor to Kaby Lake for extremely-low power mobile devices, launched concurrently with Coffee Lake and Whiskey Lake.

14nm++ for both, I guess. Skylake just won't die.

-----------------

https://en.wikichip.org/wiki/intel/process-architecture-optimization

Alder Lake seems to be built on 10nm, not sure what +/++/+++ iteration will it be. Probably a +++ since they'll have to ride 10nm for a while to break even on that money black hole. It seems it'll be the first of the Ocean Cove (WTTFtech link, click at your own risk) family of new cores. Probably what Keller was hired to help with? Finally leaving the P6 lineage behind?

Meteor Lake seems to be built on 7nm.


---------------------------------------------------------------------

Confusing as hell.

I'll proceed to give the dead horse a beating, but what the hell is up with Intel's obsession with lakes? What was wrong with their old naming of architectures around a theme? Random landmarks, Dales, Fields, Bridges, Wells....

Why do they need to throw everything into a lake? Did Krzanich have a lake fetish or something?

Will the new CEO please give whoever is in charge of naming a beating and force them to come up with more distinctive names? Please?

 

[elpokor]

I'll proceed to give the dead horse a beating, but what the hell is up with Intel's obsession with lakes? What was wrong with their old naming of architectures around a theme? Random landmarks, Dales, Fields, Bridges, Wells....

Why do they need to throw everything into a lake? Did Krzanich have a lake fetish or something?

Will the new CEO please give whoever is in charge of naming a beating and force them to come up with more distinctive names? Please?

They're following the same naming convention: every time they make a new iteration of the Core architecture (meaning: increase in IPC clock-for-clock with normalised RAM speed and timings), they switch to a new kind of landmark. Initially:

Bridges: Sandy Bridge (tock, architecture) ; Ivy Bridge (tick, new process node 22nm)
Wells: Haswell (tock, architecture) ; Broadwell* (tick, new process node 14nm)
Lakes: Skylake (tock, architecture) ; Cannon Lake*** (tick, new process node 10nm MIA)

Their fabs just screwed up big time with 10nm so Marketing Dept. took over to save the day and they came up with the Hyperscaling and Tick-Tock-Optimization shenanigans. Thus, the "Lakes" generation is adding a new member to the family for every year they fail to deliver 10nm:

Lakes: 2015Skylake (tock, architecture) ; 2016Kaby Lake (optimization, more Mhz) ; 2017Coffee Lake (optimization, moar cores) ; 2018Coffee Lake Refresh? (optimization, even moar cores)

Given the struggle they've been through with 14nm (Broadwell's launch on desktop was a joke) and given that they forecasted that 10nm will have worse transistor performance than the refined 14nm, they decided to iterate on the "optimization" thingy and thus 10nm will have no tick or new architecture until the process gets refined.

I'm guessing that adding AVX512 in consumer cores could be seen by some people as a tick, but given that Intel themselves are naming the new families Cannon Lake, Ice Lake and Tiger Lake, I wouldn't call them new architectures. So the Core family has a ton of lakes just because Intel's struggle with 14nm and 10nm:

Bridges: Sandy Bridge (tock, architecture) ; Ivy Bridge (tick, new process node 22nm)
Wells: Haswell (tock, architecture) ; Broadwell* (tick, new process node 14nm)
Lakes: 2015Skylake (tock, architecture) ; 2016Kaby Lake (optimization 14+) ; 2017Coffee Lake (optimization 14++) ; 2018Coffee Lake Refresh? (optimization) + Cannon Lake-U* (tick, new joke of a process node 10nm) ; 2019Ice Lake (optimization, 10+) ; 2020Tiger Lake (optimization, 10++)
Rapids: Sapphire Rapids, initially planned for 2020 (tock, new architecture 10++) ; Granite Rapids, initially planned for 2021 (tick, new process node 7nm presumably EUV)

No wonder why you're tired of Lakes . But as far as I'm concerned they're actually following the same naming scheme for 10 years, it's just fabs are a huge mess now so they're stuck in the same landmark until 10++ gets sorted out.

 

[jpiniero]

Next year is Comet Lake (14+++) for U and who knows for Y and S/H.

 

[scannall]

Image removed by moderator

Pics are not allowed without
personal commentary. On top of that,
this is inflammatory and does not contribute
to the thread's discussion.

AT Mod Usandthem

 

[LTC8K6]

That wouldn't stop a Corolla...