John Carmack
Member
- Sep 10, 2016
- 160
- 268
- 136
How is it "trying to bury Power9" by having barely half the threads per chip? Honest question. 52 vs 96...
Only 6 channels of DDR4 vs P9's 8, too.
KBL-R and CFL are 14nm++, SKX is 14nm+. I expect a "SKX refresh" on 14nm++, Intel said they're committing to annual product refresh for all its product lines.
The problem for Intel is all of their technological lead in transistor density never meant a damn when they tried to make mobile Atom chips much better than the ARM competition.
Segmentation hurt Atom in some areas, but not in their mobile efforts. Intel simply did too little too slow, and neither their superior process or their very deep pockets were enough to compensate.Wasn't the opinion here that segmentation was the cause for this, they did not want to eat up in big core sales?
I thought Brfoadwell-Y was 22nm, but upon further thinking and checking at AnandTech, it's actually 32nm indeed. Don't know about SKL.Good find. Isn't Intels current chipset still made on 32nm?
Brings me back to my question from a month ago : Would Coffeelake 14nm++ chips fit into the 200 series LGA 1151 socket? :/ ?Another important bit of information. Intel first gen 10nm is only slightly better than 14nm+ for transistor performance and is lower than Intel 14nm++ . In fact even Intel 10nm+ is not better than 14nm++. It will take 10nm++ to beat 14nm++ for transistor performance. (slide 29)
https://newsroom.intel.com/newsroom.../2017/03/Kaizad-Mistry-2017-Manufacturing.pdf
That does not bode well for high performance desktop CPUs from Intel based on 10nm. I think Coffeelake will probably be the fastest CPU core till 2020 in terms of clocks and single thread performance unless Icelake on 10nm+ can bring a large IPC gain to offset the lower clocks from a significantly less mature process with lower transistor performance than 14nm++.
Another interesting bit of information is Intel did not have yield information even for SRAM which they usually do while talking about a new process. Could this mean the yield problem rumours are probably true ?
Another important bit of information. Intel first gen 10nm is only slightly better than 14nm+ for transistor performance and is lower than Intel 14nm++ . In fact even Intel 10nm+ is not better than 14nm++. It will take 10nm++ to beat 14nm++ for transistor performance. (slide 29)
https://newsroom.intel.com/newsroom.../2017/03/Kaizad-Mistry-2017-Manufacturing.pdf
That does not bode well for high performance desktop CPUs from Intel based on 10nm. I think Coffeelake will probably be the fastest CPU core till 2020 in terms of clocks and single thread performance unless Icelake on 10nm+ can bring a large IPC gain to offset the lower clocks from a significantly less mature process with lower transistor performance than 14nm++.
Another interesting bit of information is Intel did not have yield information even for SRAM which they usually do while talking about a new process. Could this mean the yield problem rumours are probably true ?
Not to mention, trying to drag the mobile market to x86, locking them in to a single vendor didn't help either. I'm sure Intel has more than enough talent to make a terrific ARM mobile SOC. But, then they have to compete.Segmentation hurt Atom in some areas, but not in their mobile efforts. Intel simply did too little too slow, and neither their superior process or their very deep pockets were enough to compensate.
So, if there is a SKX refresh, then Intel will refresh it's server line on a buffed up node?
https://newsroom.intel.com/newsroom.../2017/03/Kaizad-Mistry-2017-Manufacturing.pdf
That does not bode well for high performance desktop CPUs from Intel based on 10nm. I think Coffeelake will probably be the fastest CPU core till 2020 in terms of clocks and single thread performance unless Icelake on 10nm+ can bring a large IPC gain to offset the lower clocks from a significantly less mature process with lower transistor performance than 14nm++.
Do you really think that Intel will release an Ice Lake that is slower than Coffee Lake? Come on, man.