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.

Browser: S-Browser - AnandTech Article Browser: Chrome - AnandTech Frontpage
POST A COMMENT

157 Comments

View All Comments

  • modulusshift - Tuesday, September 1, 2015 - link

    Heck yes. And of course I'm interested if anything like this is even remotely possible for Apple hardware, though likely it would require jailbreaks, at least. Reply
  • Andrei Frumusanu - Tuesday, September 1, 2015 - link

    Unfortunately basically none of the metrics measured here would be possible to extract from an iOS device. Reply
  • TylerGrunter - Tuesday, September 1, 2015 - link

    Add one more vote for the follow up with synthetics.
    I would also want to see how the multitasking compares with the Snapdragons as they use the different frequency and voltage planes per core instead of the big.LITTLE.
    But I guess that would be better to see with the SD 820, as the 810 uses big.LITTLE. Consider it a request for when it comes!
    Reply
  • tuxRoller - Wednesday, September 2, 2015 - link

    Big.little can use multiple planes for either cluster. The issue is purely implementation, tmk. Reply
  • TylerGrunter - Wednesday, September 2, 2015 - link

    big.LITTLE can be use different planes for each cluster but same for all cores in each cluster, Qualcomm SoCs can use different planes for each core, that's the difference and it's a big one.
    https://www.qualcomm.com/news/onq/2013/10/25/power...
    I'm not sure that can be done in big.LITTLE.
    Reply
  • tuxRoller - Friday, September 4, 2015 - link

    I remember that but that doesn't say that big.LITTLE can't keep each core on its own power plane just that the implementations haven't. Reply
  • soccerballtux - Tuesday, September 1, 2015 - link

    to balance everything out-- meh, that doesn't interest me. most of the time I'm concerned with battery life and every-day performance. Android isn't a huge gaming device so absolute performance doesn't interest me. Reply
  • porphyr - Tuesday, September 1, 2015 - link

    Please do! Reply
  • ppi - Tuesday, September 1, 2015 - link

    Go ahead. This is one of the most interesting performance digging on this site since the random-write speeds on SSDs. Reply
  • jospoortvliet - Friday, September 4, 2015 - link

    Yes, this was an awesome and interesting read. Reply

Log in

Don't have an account? Sign up now