Cortex A15: SunSpider 0.9.1

SunSpider performance in Chrome on the Nexus 10 isn't all that great to begin with, so the Exynos 5250 curve is longer than the competition. I wouldn't pay too much attention to overall performanceas that's more of a Chrome optimization issue, but we begin to shine some light on Cortex A15's power consumption:

Although these line graphs are neat to look at, it's tough to quantify exactly what's going on here. Following every graph from here on forward I'll present a bar chart that integrates over the benchmark time period (excluding idle) and presents total energy used during the task in Joules.

Task Energy - SunSpider 0.9.1 - Total Platform

The data here reflects what you see in the chart above fairly well. Acer/Intel manage to get the edge over Dell/Qualcomm when it comes to total energy consumed during the test. The Nexus 10 doesn't do so well here but that's likely a software issue more than anything else.

CPU power is just insane. Peak power consumption is around 3W, compared to around 1W for the competition.

Task Energy - SunSpider 0.9.1 - CPU Only

Looking at the CPU core itself, Qualcomm appears to have the advantage here but keep in mind that we aren't yet tracking L2 cache power on Krait (but we are on Atom). Regardless Atom and Krait are very close.

Even GPU power consumption is pretty high compared to everything else (minus Tegra 3).

Task Energy - SunSpider 0.9.1 - GPU Only

SunSpider - Max, Avg, Min Power

For your reference, the remaining graphs present max, average and min power draw throughout the course of the benchmark (excluding beginning/end idle times).

Max Power Draw - SunSpider 0.9.1 - Total Platform

Max Power Draw - SunSpider 0.9.1 - GPU Only

Max Power Draw - SunSpider 0.9.1 - CPU Only

Average Power Draw

Average Power Draw - SunSpider 0.9.1 - Total Platform

Average Power Draw - SunSpider 0.9.1 - GPU Only

Average Power Draw - SunSpider 0.9.1 - CPU Only

Minimum Power Draw

Min Power Draw - SunSpider 0.9.1 - Total Platform

Min Power Draw - SunSpider 0.9.1 - GPU Only

Min Power Draw - SunSpider 0.9.1 - CPU Only

ARM's Cortex A15: Idle Power Cortex A15: Kraken
POST A COMMENT

140 Comments

View All Comments

  • powerarmour - Friday, January 04, 2013 - link

    So yes, finally confirming what anyone with half a brain knows, competitive ARM SoC's use less power. Reply
  • apinkel - Friday, January 04, 2013 - link

    I'm assuming you are kidding.

    Atom is roughly equivalent to (dual core) Krait in power draw but has better performance.

    The A15 is faster than either krait or the atom but it's power draw is too much to make it usable in a smartphone (which is I'm assuming why qualcomm had to redesign the A15 architecture for krait to make it fit into the smartphone power envelope).

    The battle I still want to see is quad core krait and atom.
    Reply
  • ImSpartacus - Friday, January 04, 2013 - link

    Let me make sure I have this straight. Did Qualcomm redesign A15 to create Krait? Reply
  • djgandy - Friday, January 04, 2013 - link

    No. Qualcomm create their own designs from scratch. They have an Instruction Set licence for ARM but they are arm "clones" Reply
  • apinkel - Friday, January 04, 2013 - link

    Sorry, yeah, I could have worded that better.

    But in any case the comment now has me wondering if I'm off base in my understanding of how Qualcomm does what it does...

    I've been under the impression that Qualcomm took the ARM design and tweaked it for their needs (instead of just licensing the instruction set and the full chip design top to bottom). Yeah/Nay?
    Reply
  • fabarati - Friday, January 04, 2013 - link

    Nay.

    They do what AMD does, they license the instruction set and create their own cpus that are compatible with the ARM ISA's (in Krait's case, the ARMv7). That's also what Apple did with their Swift cores.

    Nvidia tweaked the Cortex A9 in the Tegra 2, but it was still a Cortex A9. Ditto for Samsung, Hummingbird and the Cortex A8.
    Reply
  • designerfx - Friday, January 04, 2013 - link

    do I need to remind you that the Tegra 3 has disabled cores on the RT? Using an actual android device with Tegra 3 would show better results. Reply
  • madmilk - Friday, January 04, 2013 - link

    The disabled 5th core doesn't matter in loaded situations. During idle, screen power dominates, so it still doesn't really matter. About all you'll get is more standby time, and Atom seems to be doing fine there. Reply
  • designerfx - Friday, January 04, 2013 - link

    The core allows a lot of different significant things - so in other words, it's extremely significant, including in high load situations as well.

    That has nothing to do with the Atom. You get more than standby time.
    Reply
  • designerfx - Friday, January 04, 2013 - link

    also, during idle the screen is off, usually after whatever amount of time the settings are set for. Which is easily indicated in the idle measurements. What the heck are you even talking about? Reply

Log in

Don't have an account? Sign up now