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
Play Store Open & Scroll
The little cores all have significant load placed onto them. It looks like the app multi-threads well in this scenario and the little threads are well fitted to accomodate the load that is placed onto them.
Surpsingly, we also see the big CPUs having some continuous load. The app launch itself triggers the big cluster to go to full speed of 2.1GHz and migrate threads onto all 4 CPUs. Scrolling through the page also loads at least 1 significant big thread. The CPU's frequency remains quite moderate though as we only see some small bursts to up to 1GHz while the rest of the time the big cores idle on the minimum 800MHz frequency.
Overall, the Play Store app also seems to be optimized and aimed for 4-core designs. Here big.LITTLE seems to work well as we see a mix of small threads with a mix of big threads running concurrently on both clusters.
157 Comments
View All Comments
Hrobertgar - Tuesday, September 1, 2015 - link
Your spikes on the video recording appear to be every ~4 secs of video, could the CPU spikes be app / memory related?badchris - Tuesday, September 1, 2015 - link
Thank you for this excited article.And one problem,how do we explain 2 big core Snapdragon 808 is more efficient than 4 big core Snapdragon 810?Andrei Frumusanu - Tuesday, September 1, 2015 - link
You cannot make comparisons between different SoCs even if they have the same CPU IP and the same manufacturing process. The S808 is different from the S810 which are again different from Nvidia's X1 even if all 3 have A57 cores on TSMC 20nm.badchris - Tuesday, September 1, 2015 - link
nvm,i should realize this comparison is not scientific.metafor - Tuesday, September 1, 2015 - link
The S808 and S810 should be fairly similar though. That's not to say you can say that the only difference is the CPU configuration but a similar study on what the behavior is like on a different SoC with fewer cores would be helpful.Threading isn't 100% free and neither is thread migration. It might be good to take a look at just what the S810 is doing over time compared to the S808 in terms of CPU activity.
Andrei Frumusanu - Tuesday, September 1, 2015 - link
I have data on all of that... It's just in need of being published in an orderly fashion.kpkp - Tuesday, September 1, 2015 - link
There are quite few other differences beside the 2 cores, starting with the memory controller.badchris - Tuesday, September 1, 2015 - link
thx for your notice.there're something i forgotnpp - Tuesday, September 1, 2015 - link
As an ex-Android developer I can remember that the SDK not only encourages, but sometimes straight out enforces extensive usage of threads. For example, around API level 14/15, making a network request in the main thread would throw an exception, which may seem obvious to experienced developers but wasn't enforced in earlier versions. This is a simple example, but having the API itself pushing towards multi-threaded coding has a positive effect on the way Android developers build their apps. I'm not sure then why Google's own browser would be surprising for its usage of high thread counts - even a very basic app would be very likely to spawn much more than 4 threads nowadays.Arbie - Tuesday, September 1, 2015 - link
"I was weary of creating this table..."That's not surprising, after all your work ;-).
Terrific article BTW which is up to Anandtech's long-time standards. Seems like a mini master's thesis.