3 ms·
Not sure ‘already’ is appropriate here. big.LITTLE was announced in 2011. Taking 11 years to copy a competitor’s successful feature must be a record of some sor
by klelatti 5y ago
Not sure ‘already’ is appropriate here. big.LITTLE was announced in 2011. Taking 11 years to copy a competitor’s successful feature must be a record of some sort.
- Kon-Peki 5y agoNot sure you understand the point of big.LITTLE. It's about dealing with power and thermal constraints in the quest for more performance [1]. So was the transition to multicore processors, BTW [2]. These are the things hardware companies do when they have no other option. And as [2] points out, we software folks still don't have a good way to deal with it. [1] https://armkeil.blob.core.windows.net/developer/Files/pdf/white-paper/big-little-technology-the-future-of-mobile.pdf https://armkeil.blob.core.windows.net/developer/Files/pdf/wh... [2] https://www2.eecs.berkeley.edu/Pubs/TechRpts/2006/EECS-2006-183.pdf https://www2.eecs.berkeley.edu/Pubs/TechRpts/2006/EECS-2006-... Alder Lake is about dealing with power and thermal constraints. Intel has finally pushed performance so far that they need to do this. The chips are benchmarking so well because of this move, not in spite of it.
- klelatti 5y agoI do know what big.LITTLE is about thanks. No idea why you’d think otherwise from my post. Of course Alder Lake is benchmarking well because of it. My point was ‘already’ makes it sound like Intel is rapidly adopting this technology - not 11 years after Arm.