The Mobile CPU Core-Count Debate: Analyzing The Real World
by Andrei Frumusanu on September 1, 2015 8:00 AM EST- Posted in
- Smartphones
- CPUs
- Mobile
- SoCs
S-Browser - AnandTech Frontpage
Again staying with the S-Browser, we check the behaviour of just pure web-page rendering. This time we load the AnandTech front-page without scrolling through the page. The page is slightly heavier as we have more graphical elements as opposed to text on the previous article page.
This time around, we a more even distribution of the load on the little cores. Again, most of the 4 CPU cores are active and have threads placed onto them, averaging about 2.5 fully loaded cores.
The frequency distribution is much more variable in this scenario, as the cluster makes wide usage of the frequency range available to itself. On the power state distribution chart we see that most CPUs are still able to enter their power-gating states, indicating that we're mostly handling very short bursty loads.
The biges cores seems much less loaded in this scenario, as most of the time except for a small peak we only have 1 large thread loading the cluster. Because of this, we expect the other cores to be shut down and if we look at the power state distribution we guessed correctly.
The total amount of threads on the system doesn't change much compared to the previous scenario: The S-Browser still manages to actively make good use of up to 4 cores with the occasional burst of up to 5 threads.
Facebook
Twitter
RSS
157 Comments
View All Comments
yankeeDDL - Tuesday, September 1, 2015 - link
Just wanted to say that it's agreat article. Well done and very interesting: the use of 4+4 cores on a mobile platform while on a PC we still have plenty of 2 cores CPUs, seemed quite ridiculous. But no, clearly, it makes sense.Tolwyns - Tuesday, September 1, 2015 - link
Very interesting article. These test were done on Android 5, I take it. I know that this analysis is geared toward current hardware, but most of the "4cores are only marketing" discussion was quite a while back when most device had some version of Android 4. I wonder if the benefits of more cores did show up then. The second thing i'm interested in is "How much of this is applicable to other SOCs". Not much I gather. And related to that "How much of this is limited to Samsung devices", because they made the CPU and the Firmware-softwarelayer of the tested device.SunLord - Tuesday, September 1, 2015 - link
I'm kinda curious how a 8 core version of the x20 with 2 lower power 4 mid power and 2 high power cores would performShadowmaster625 - Tuesday, September 1, 2015 - link
It is kind of a misleading analysis. One single haswell core could juggle all of these processes and still have plenty of time to sleep. So you're not really telling us anything here. Is a wider fatter core better than all these narrow underpowered cores? Given the performance and power consumption of the apple SoCs, I would still have to say yes.IanHagen - Tuesday, September 1, 2015 - link
This! When developing for iOS I usually have to span several threads (queues in Apple's world) for things that would otherwise block the main queue, which would cause the UI to "freeze" and the dual core SoC inside the devices I'm targeting are munching my threads absolutely fine. Just by saying that the several extre cores found in Android phones aren't sleeping you're not coming to any definitive conclusion about any clear advantage of having them.nightbringer57 - Tuesday, September 1, 2015 - link
The thing is that when you have 4 threads, 4 cores can potentially do the job more efficiently with performance equal to a single core with 4 times the execution speed.nightbringer57 - Tuesday, September 1, 2015 - link
*by efficiently, I mean, using less power*metafor - Tuesday, September 1, 2015 - link
Potentially, but not necessarily. Threading and thread migration aren't free. It depends on how much performance you really need. The A57(R3), for instance, at very low frequencies is actually slightly more power efficient than the A53 at its peak frequency (surprising, I know).If you have 4 threads that need absolutely-bare-minimum performance that a min-frequency single-core could handle, waking up 4 cores (even if they're smaller) and loading the code/data into the caches of each of those cores isn't necessarily a clear win. Especially if they share the same code.
lilmoe - Tuesday, September 1, 2015 - link
"The A57(R3), for instance, at very low frequencies is actually slightly more power efficient than the A53 at its peak frequency (surprising, I know)."Cool story. Except that, in most of the smaller multithreaded workload cases, the little cores usually aren't near their saturation levels. Also, in most cases, when they _do_ get saturated, the workload is transferred and dealt with by big core or two in short bursts.
Even if it isn't a "clear win", in *some* workloads mind you, saying that there isn't any apparent merit in these configurations is really irresponsible.
metafor - Tuesday, September 1, 2015 - link
I don't think I said there's no merit to such configurations. I simply said parallelizing a workload isn't always a clear win over using a single core. It depends on the required performance level and the efficiency curve of the small core and big core.If 4 threads running on 4 small cores at 50% FMax can be done by one big core at FMin without wasting any cycles, the advantage actually goes to the big core configuration. The small core configuration works if there's a thread that requires so little performance, it'd be wasteful to run it on the big core even at FMin.
The conclusion of which is best for the given workload isn't as clear cut as saying "look, the small cores are being used by a lot of threads!". But rather, by measuring power and perf using the two configurations.