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

  • kyuu - Friday, January 4, 2013 - link

    You're the one stepping into the past with the CISC vs. RISC. x86 is not going to go away anytime soon. Keep dreaming, though. Reply
  • iwod - Saturday, January 5, 2013 - link

    Nothing about Architectures in this comment, but by the time ARM Cortex A57 is out, so is Intel ValleyView, which doubles the performance. A57 is expected to give in best case scenario 30 - 50% increase in performance. And All of a sudden this look so similar to 2x Atom performance.

    It will only take one, just ONE mistake that ARM make for Intel to possibly wipe them off the map.

    Although looking into the next 3 - 5 years ahead. It will be a bloody battle instead.
    Reply
  • Cold Fussion - Friday, January 4, 2013 - link

    Why didn't have any charts which were performance per watt or energy consumption vs performance in the GPU area? If the Mali chip is using twice the energy but giving 3x the performance then that is a very significant point thats being misrepresented. Reply
  • mrdude - Friday, January 4, 2013 - link

    I was thinking the same thing.

    If I can game at native resolution on a Nexus 10 at better frame rates than on the Atom or Snapdragon SoC and the battery capacity is larger and the price of the device is equal, then do I really care about the battery life?

    Although it's nice seeing Intel is getting x86 down to a competitive level with ARM, the most astonishing thing that I took away from that review was just how amazing that MaliT604 GPU is. All that performance and only that power draw? Yesplz :P
    Reply
  • parkpy - Friday, January 4, 2013 - link

    i've learned so much from AT's review of the iPhone5, Galaxy S III, and Nexus 4, and this article about mobile phones that it makes me wish AT could produce MORE reviews of mobile devices.

    All of this information is crack! I can't get enough of it. Keep up the good work! And Intel, I can't wait for you to get your baseband processor situation sorted out!

    I was already tempted to get a Razr I, but it looks like before the end of the year consumers will have some very awesome technology in their phones that won't require as much time on the battery charger!
    Reply
  • This Guy - Friday, January 4, 2013 - link

    What if Rosepoint is software defined instead of fixed function? Reply
  • ddriver - Friday, January 4, 2013 - link

    I am confused here - this review shows the atom to be somewhat faster than A15, while the review at phoronix shows the A15 destroying the atom, despite the fact intel's compiler is incredibly good at optimizations and incomparably more mature.

    So I am in a dilemma on who to trust - a website that is known to be generously sponsored by intel or a website that is heavily focused on open source.

    What do you think?
    Reply
  • kyuu - Friday, January 4, 2013 - link

    Uh, did we read the same article? Where does it show the Atom being "somewhat faster than A15"? The article showed that the A15 is faster than Atom, but at a large power premium. Reply
  • ddriver - Friday, January 4, 2013 - link

    On the charts I see the blue line ending its task first and taking less time, blue is atom, right? Reply
  • jwcalla - Friday, January 4, 2013 - link

    A couple things:

    1) The Phoronix benchmarks were for different Atoms than the one used in this article. I don't know how they compare, but they're probably older models.

    2) The Phoronix benchmarks used GCC 4.6 across the board. Yes, in general GCC will have better optimizations for x86, but we don't know anything (unless I missed it) about which compilers were used here. If this was an Intel sample sent to Anand, I'm sure they compiled the software stack with one of their own proprietary Intel compilers. Or perhaps it is the MS compiler, which no doubt has decades of x86 optimizations built in and probably less ARM work than GCC (for the RT comparison).

    Don't take the benchmarks too seriously, especially since even the software isn't held constant here like it was in the Phoronix benchmarks. It's all ballpark information. Atom is competitive with ARMv7 architectures -- that's the takeaway.
    Reply

Log in

Don't have an account? Sign up now