Camera Launching

I wanted also to have a closer look at CPU behaviour while using the phone's camera. First off, we start off by analyzing what happens when we launch the camera application.

Nothing much to report on the little cores, we only see some minor load on a couple of threads while the camera is running.

Most of the work when launching the camera was done by the big cluster. Here we see all 4 cores jumping into action. It's interesting to see that at these smaller time-scales we can observe how the CPU frequency lags behind the actual load on the cluster, as the frequency governor maintains a higher frequency for some time before falling back to the idle 800MHz.

Samsung seems to be able to parallelize well the camera application as this is again a sensible scenario that makes good usage of the 4.4 big.LITTLE topology of the SoC.

App: Play Store App Updates Camera: Still Snapshot
Comments Locked

157 Comments

View All Comments

  • TylerGrunter - Tuesday, September 1, 2015 - link

    In fact you are in the right place to ask that question, as one of the profets os the mantra was Anand Lal Shimpi himself:
    http://www.anandtech.com/show/7335/the-iphone-5s-r...
    Quoting from the article:
    "two faster cores are still better for most uses than four cores running at lower frequencies"
    You can read the rest if you are interested, but that´s how much of the mantra started.
  • retrospooty - Tuesday, September 1, 2015 - link

    I wont hold that against Anand, he was lobbying toward a job at Apple ;)

    But seriously, it was 2 years ago. At that time ""two faster cores are still better for most uses than four cores running at lower frequencies" may well have been the case. Also, no matter how you slice it, an 8 core big.little is not a true 8 core CPU. It's really still 4 cores.
  • retrospooty - Tuesday, September 1, 2015 - link

    /edit. I do remember alot of people crying "you dont need 8 cores" but again, that was people misunderstanding ARM's big.little architecture made worse by marketing calling it "8" cores" in the first place.
  • TylerGrunter - Tuesday, September 1, 2015 - link

    I agree with you, and he may not have been THAT wrong at the time. But with the current implementations of power gating and turbos most of what he said has been rendered false.
    AFAIK, big.LITTLE can be a true 8 core, it actually depends on the implementation.
  • lilmoe - Sunday, September 6, 2015 - link

    "Also, no matter how you slice it, an 8 core big.little is not a true 8 core CPU. It's really still 4 cores."

    An 8 core big.LITTLE chip running in HMP mode (like the Exynos 5422 onward) is in fact a "true" 8 core chip in which all 8 cores can be running at the same time. You're thinking core migration and cluster migration setups in which only 4 cores (or a combination of 4) can be running at the simultaneously.
  • lilmoe - Sunday, September 6, 2015 - link

    "can be running at the simultaneously."
    *corrected: can be running simultaneously.
  • osxandwindows - Friday, September 25, 2015 - link

    If i run all 8 cores at the same time, wood it affect battery life?
  • mkozakewich - Wednesday, September 2, 2015 - link

    If the option is really four weak cores or two powerful cores, I think the two powerful ones would make a better system. If we could have two powerful cores AND four weak cores, that would be even better.

    So I think he was probably justified.
  • mkozakewich - Wednesday, September 2, 2015 - link

    Just everyone who's easily influenced, really. I heard it from pretty much everyone. Someone I was talking to apparently "knew someone who designed a Galaxy phone." He claimed they wanted to design it with two cores, or something, but the marketers wanted eight.
  • StormyParis - Tuesday, September 1, 2015 - link

    Very interesting, thank you.

Log in

Don't have an account? Sign up now