ARM Vs. x86: The Secret Behind Intel Atom's Efficiency

Intel's Video Playback Results Compared To Ours

We then had the chance to look at power consumption during media playback.

Swipe to scroll horizontally
Microsoft Surface
Row 0 - Cell 0 FPSPlatform (W)CPU (W)GPU (W)Memory (W)Panel Backlight (W)Everything Else (W)
Local 1080p H.264 @ 20 Mb/s304.210.350.510.580.881.90
Local 1080p H.264 @ 20 Mb/s (Split Screen)304.870.570.590.611.112.00
Stream HTML5 Playback305.370.690.780.890.902.10
Stream HTML5 Playback (Split Screen)306.10.920.920.941.102.22
Swipe to scroll horizontally
Acer W510
Row 0 - Cell 0 FPSPlatform (W)CPU (W)GPU (W)Memory (W)Panel Backlight (W)Everything Else (W)
Local 1080p H.264 @ 20 Mb/s303.500.170.370.450.891.62
Local 1080p H.264 @ 20 Mb/s (Split Screen)304.030.370.330.451.191.69
Stream HTML5 Playback303.950.300.390.470.981.81
Stream HTML5 Playback (Split Screen)304.770.680.340.471.272.01
Local Stress Test (+McAfee)29.85.931.390.420.561.192.37
Stream HTML5 Stress Test (+McAfee)29.86.001.290.430.591.272.43

It's interesting to look at the impact of adding a McAfee antivirus scan to the video playback workload. Due to security flaws in older versions of Windows Media Player, the software has to scan the video file itself for malware. On our Acer tablet, we see an initial stutter while opening the video clip (while it's being scanned, resulting in dropped frames). Things smooth out after that, though.

When it comes to total platform power consumption, Acer's W510 has the edge over Microsoft's Surface. Once again, comparing processor power consumption, we know that the Tegra 3 offers superior idle results thanks to its 4-PLUS-1 architecture. But the moment a workload is applied, the Atom fares better. 

The GPU consumption column is also interesting. Intel's Atom uses less power during local and HTML5-based video playback, and when the screen is split, the difference is even greater. It's not clear whether this is related to the fixed-function hardware acceleration for H.264, or some other variable (like drivers, where Nvidia could be expected to have an advantage). 

As we noted on the previous page, there appears to be magic happening on Intel's memory controller. From best- to worst-case scenario (including a workload that wasn't even run on Tegra 3), the Atom requires a 31% increase in power; the Tegra comes close to doubling its power consumption from its best- to worst-case scenario. As the workload gets more demanding and the tablet isn't reading from memory in a purely linear fashion, Intel's two 32-bit controllers maintain lower consumption. Nvidia's single-channel controller, operating at higher data rates, isn't able to follow suit.

Verifying Intel's Numbers, In-House

Frankly, it's going to be difficult for anyone to replicate Intel's lab work, based on the equipment we saw set up in Santa Clara. But the numbers presented by Intel seem plausible. With a smaller 26.6 Wh battery in the Acer W510, plus the keyboard dock (around 53.2 Wh), 1080p video should play back for 15.2 hours based on the 3.5 W figure. My 1080p test lasted for 15 hours and 37 minutes (with the volume at 10%). So, again, the results are believable.

In contrast, Microsoft's Surface is reported as requiring 4.21 W. With its 31.5 Wh battery, that'd theoretically be up to 7.48 hours of playback. In Microsoft Surface Review, Part 2: Battery Life, Multi-Monitor, And More, Andrew measured 7 hours and 10 minutes at maximum brightness (4.4 W) and 10 hours at 200 nits with the Wi-Fi radio disabled (3.15 W). This really shows how much the display and other platform components can affect run time, and how much bit rate appears to affect the Tegra 3. What do we mean? Well, our in-house test file is a 6 Mb/s H.264-encoded file running at 720p, as opposed to Intel's 20 Mb/s test at 1080p.

We get 8.95 hours from an iPad 2 (25 Wh battery) and 7.92 hours from a third-gen iPad (42.5 Wh battery). This puts power consumption at 2.8 W and 5.37 W for each device, respectively, at maximum brightness. At 200 nits, we get 12.35 hours from the iPad 2 and 11.28 hours from the third-gen iPad, translating to 2.02 W and 3.77 W during the video workload, again, respectively. This means that the third-gen iPad appears to consume more power playing back a 6 Mb/s 720p video clip than the Atom with a 20 Mb/s 1080p file.

Under those same Tom’s Hardware 720p test conditions, the Tegra 3-powered Asus Transformer Prime (25 Wh battery) yields 8.33 hours at maximum brightness (3.00 W) and 10.8 hours at 200 nits (2.31 W). Compared directly against the Surface, this suggests that the Transformer Prime is thriftier with power, likely due to a combination of Android versus Windows RT and differences in both devices' screens. 

Google's Nexus 10 is advertised as doing nine hours of video playback from a 33.75 Wh battery, which calculates out to 3.75 W for a 4 MP display. We’ll be revising the Nexus 10 numbers later.

  • Novuake
    Excellent! Was wondering about this for some time. Also made the mistake of thinking Intel was behind in the mobile space... Well done Toms.
    Reply
  • tipoo
    I'll be very interested to read the Cortex A15 follow up. From what I gather, if compared on the same lithography the A15 core is much larger than the A9, which likely means more power, all else being equal. It brings performance up to and sometimes over the prior generation Atom, but I wonder what power requirement sacrifices were made, if any.

    I'm thinking in the coming years, Intel vs ARM will become a more interesting battle than Intel vs AMD.
    Reply
  • AlanDang
    @tipoo, we're not going to hang our hat on it just yet (until we run the numbers ourselves), but A15 runs hot, which is what we hint at in our article.
    Reply
  • blubbey
    tipoo I'm thinking in the coming years, Intel vs ARM will become a more interesting battle than Intel vs AMD.
    I was until I saw the numbers. Intel spent $8.4 billion in 2011 ($6.6 billion in 2010 and $5.7 billion in 2009) on R&D - http://www.intc.com/intelAR2011/business/research/ - while ARM isn't worth $1b. It may take a few years but Intel are seriously massive, they'll soon be the go to guys for mobile. Plus (according to rumours) with Haswell focusing on power saving, it could be a big leap forward.
    Reply
  • tipoo
    AlanDang@tipoo, we're not going to hang our hat on it just yet (until we run the numbers ourselves), but A15 runs hot, which is what we hint at in our article.
    I'm guessing the same thing. So far we've only seen it in a tablet (Nexus 10), and even that with its 10 inch tablet sized battery didn't last particularly long. ARM has the distribution advantage right now, but I think once Intel gets its foot in the door it will be the 900lb gorilla in this market as well.
    Reply
  • ARM isn't just ARM holdings, it's nVidia, Samsung, and Qualcomm just to name a few of the heavy hitters. And it should also be noted that even if your SoC is better, if the OEM integrating it is incompetent, it won't matter. I'm certain more Surface RT devices have been sold compared to the Acer W500 because it had better availability, a stronger marketing campaign, and overall is a far more solid device. Don't miss the forest for the trees.
    Reply
  • tipoo
    blubbeyI was until I saw the numbers. Intel spent $8.4 billion in 2011 ($6.6 billion in 2010 and $5.7 billion in 2009) on R&D - http://www.intc.com/intelAR2011/business/research/ - while ARM isn't worth $1b. It may take a few years but Intel are seriously massive, they'll soon be the go to guys for mobile. Plus (according to rumours) with Haswell focusing on power saving, it could be a big leap forward.
    Didn't Qualcomm alone overtake AMD as a chipmaker? The thing about ARM is that anyone can get a licence for the ISA and build a custom core around it, like Krait.
    Reply
  • AlanDang
    And the Chromebook with an A15. We're looking at several other SoC's but what's empowering is how simple math can help you look at efficiency.

    But it's Christmas Eve, and sometimes there are more important things than running benchmarks and soldering wires to SoCs. ;)
    Reply
  • richarduk
    Measurements taken when running Windows. Arm and Intel chips both require different coding styles to make them preform. The way windows has been coded favours the Intel Arch. Intel chips like to lean heavy on their cache, Arm chips prefer code to do as much processing on it's data as it can using all it's registers before moving on.

    Bit like comparing a 4x4 and a sports car in a muddy field.

    Reply
  • darkchazz
    nvidia tegra 3 is a piece of overhyped garbage.
    Reply