Hangouts Writing A Message

Naturally typing and writing messages is a big part of every-day scenarios for a lot of applications. This time, it's mostly the keyboard application that uses up most of the processing power as it does dictionary lookups for word correction and prediction. In this scenario I used TouchPal's swyping keyboard instead of a usual touch keyboard. 
 
No I don't usually swype this slowly!

On the little cores we see a very variable load. In general, it looks like all 4 little cores are used at medium load. CPU frequency as well doesn't look to reach the higher frequency states and tends to fluctuate on the lower-end of the available range.

The big cores aren't active at all. It's only when sending the message that the cores kick into gear for a very short burst. The rest of the time, they're residing on at minimim frequency in their power-gated states.

As the big cores didn't have much scheduled on them, the total rq-graph for the whole system doesn't look very different from the one on the little cores. Writing messages is definitely a low-end task that doesn't require too much processing power.

App: Hangouts Launch App: Reddit Sync Launch
Comments Locked

157 Comments

View All Comments

  • lilmoe - Tuesday, September 1, 2015 - link

    "if the interest is high enough"

    :/ Really?
  • zaza - Saturday, September 5, 2015 - link

    Yes Please. It would be nice to see if the same or similar tests works on snaprdagon 810,801 and 615 and Mediatek chips, and intel SoC
  • erchni - Thursday, September 17, 2015 - link

    A follow-up with synthetic would be quite interesting.
  • aryonoco - Saturday, September 5, 2015 - link

    I just wanted to reiterate the point here an thank the author for this great piece of technical investigative journalism.

    Andrei, thank you for this work. It is hugely invaluable and insightful.
  • tipoo - Tuesday, September 1, 2015 - link

    Very interesting article. Seems like the mantra of "more cores on mobile are just marketing" was wrong in terms of Android, seems to dip into both four core big and little clusters pretty well. That puts the single thread performance having lagged behind the Apple A series (up until the S6 at least) in a new light, since it can in fact use the full multicore performance.
  • tipoo - Tuesday, September 1, 2015 - link

    *That is, barring gaming. More core Android functions do well with multithreading though.
  • jjj - Tuesday, September 1, 2015 - link

    In gaming there is a big advantage. By using mostly the small cores you allow for more TDP to go to the GPU. One more relevant thing would console ports in the next couple of years when mobile GPUs will catch up with consoles. The current consoles have 8 small cores and that fits just right with many small cores in Android.
  • retrospooty - Tuesday, September 1, 2015 - link

    Not really sure whos "mantra" that was. People that don't understand what the big.little architecture is like some angry Apple fans?
  • tipoo - Tuesday, September 1, 2015 - link

    Well sure, whoever they were, but it was a pretty common refrain for every 8 core SoC.
  • soccerballtux - Tuesday, September 1, 2015 - link

    for one, it was my mantra. I liked having 4 cores because 2 wasn't enough, but according to my hotplugging times, I only really need 3 for optimal experience most of the time

Log in

Don't have an account? Sign up now