The future of software is multithreaded. Current software that was optimized for single threaded work will become obsolete, and providing hardware that has single cores will hold back progress. More cores and more threads = faster, better.
The majority of smart phone users in general would be better off with a dumb phone, so that makes your argument irrelevant.
You actually have it backwards. Faster cores = more heat, more cores = less heat. Although heat in general has many determining factors and cannot be simplified as such. But anytime you increase the clockspeed of a chip, you have to raise the voltage, and more voltage equals more heat. Anybody who?s ever overclocked anything can attest to this.
Oh, and give me ONE scenario where a dual-core is faster than a quad-core FROM THE SAME ARCHITECTURE.
Try this article from anandtech. TL; DR - the scenario you mentioned may be possible, but the problem is that no one is doing it now, and the writing is up in the air as to whether anyone will do it in the near future.
http://www.anandtech.com/show/7335/the-iphone-5s-review/2
Specifically, this part.
I always thought the transition from 2 to 4 cores happened quicker in mobile than I had expected. Thankfully there are some well threaded apps that have been able to take advantage of more than two cores and power gating keeps the negative impact of the additional cores down to a minimum. As we saw in our Moto X review however, two faster cores are still better for most uses than four cores running at lower frequencies. NVIDIA forced everyone?s hand in moving to 4 cores earlier than they would?ve liked, and now you pretty much can?t get away with shipping anything less than that in an Android handset. Even Motorola felt necessary to obfuscate core count with its X8 mobile computing system. Markets like China seem to also demand more cores over better ones, which is why we see such a proliferation of quad-core Cortex A5/A7 designs. Apple has traditionally been sensible in this regard, even dating back to core count decisions in its Macs. I remembering reviewing an old iMac and pitting it against a Dell XPS One at the time. This was in the pre-power gating/turbo days. Dell went the route of more cores, while Apple chose for fewer, faster ones. It also put the CPU savings into a better GPU. You can guess which system ended out ahead.
In such a thermally constrained environment, going quad-core only makes sense if you can properly power gate/turbo up when some cores are idle. I have yet to see any mobile SoC vendor (with the exception of Intel with Bay Trail) do this properly, so until we hit that point the optimal target is likely two cores. You only need to look back at the evolution of the PC to come to the same conclusion. Before the arrival of Nehalem and Lynnfield, you always had to make a tradeoff between fewer faster cores and more of them. Gaming systems (and most users) tended to opt for the former, while those doing heavy multitasking went with the latter. Once we got architectures with good turbo, the 2 vs 4 discussion became one of cost and nothing more. I expect we?ll follow the same path in mobile.
Then there?s the frequency discussion. Brian and I have long been hinting at the sort of ridiculous frequency/voltage combinations mobile SoC vendors have been shipping at for nothing more than marketing purposes. I remember ARM telling me the ideal target for a Cortex A15 core in a smartphone was 1.2GHz. Samsung?s Exynos 5410 stuck four Cortex A15s in a phone with a max clock of 1.6GHz. The 5420 increases that to 1.7GHz. The problem with frequency scaling alone is that it typically comes at the price of higher voltage. There?s a quadratic relationship between voltage and power consumption, so it?s quite possibly one of the worst ways to get more performance. Brian even tweeted an image showing the frequency/voltage curve for a high-end mobile SoC. Note the huge increase in voltage required to deliver what amounts to another 100MHz in frequency.
The combination of both of these things gives us a basis for why Apple settled on two Swift cores running at 1.3GHz in the A6, and it?s also why the A7 comes with two cores running at the same max frequency. Interestingly enough, this is the same max non-turbo frequency Intel settled at for Bay Trail. Given a faster process (and turbo), I would expect to see Apple push higher frequencies but without those things, remaining conservative makes sense. I verified frequency through a combination of reporting tools and benchmarks. While it?s possible that I?m wrong, everything I?ve run on the device (both public and not) points to a 1.3GHz max frequency.
Sent from my iPad using Tapatalk HD