Increased Dynamic Range: Understanding the Power Profile of Modern SoCs

Section by Anand Shimpi

The iPhone 4S greatly complicated the matter of smartphone power consumption. With the A5 SoC Apple introduced a much wider dynamic range of power consumption to the iPhone than we were previously used to. Depending on the workload, the A5 SoC could either use much more power than its predecessor or enjoy decreased overall energy usage. I began our battery life analysis last time with some graphs showing the power savings realized by a more power hungry, faster CPU.

The iPhone 5 doesn't simplify things any more. I believe the days of us having straightforward discussions about better/worse battery life are long gone. We are now firmly in the era of expanded dynamic range when it comes to smartphone power consumption. What do I mean by that? The best way to explain is to look at some data. The graphs below show total device power consumption over time for a handful of devices running the Mozilla Kraken javascript benchmark. Kraken is multithreaded and hits the CPU cores fairly well. The power profile of the benchmark ends up being very similar to loading a very js-heavy web page, although for a longer period of time. All of the device displays were calibrated to 200 nits, although obviously larger displays can consume more power.

Let's start out by just looking at the three most recent iPhone generations:

The timescale for this chart is just how long the iPhone 4 takes to complete the Kraken benchmark. The iPhone 4/4S performance gap feels a lot bigger now going back to the 4 than it did when the 4S launched, but that's how it usually seems to work. Note how tight the swings are between min and max power consumption on the iPhone 4 during the test. As a standalone device you might view the iPhone 4 as being fairly variable when it comes to power consumption but compared to the 4S and 5 it might as well be a straight line.

The 4S complicated things by consuming tangibly more power under load than the 4, but being fast enough to complete tasks in appreciably less time. In the case of this Kraken run, the 4S consumes more power than the 4, however it's able to go to sleep quicker than the 4 and thus draw less power. If we extended the timeline for the iPhone 4 significantly beyond the end of its benchmark run we'd see the 4S eventually come out ahead in battery life as it was able to race to sleep quicker. The reality is that with more performance comes increased device usage - in other words, it's highly unlikely that with a 50% gain in performance users are simply going to continue to use their smartphone the same way as they would a slower device. Usage (and thus workload) doesn't remain constant, it's somewhat related to response time.

The iPhone 5 brings new meaning to device level power consumption. With a larger display and much more powerful CPU, it can easily draw 33% more power than the 4S under load, on average. Note the big swings in power consumption during the test. The A6 SoC appears to be more aggressive in transitioning down to idle states than any previous Apple SoC, which makes sense given how much higher its peak power consumption can be. Looking at total energy consumed however, the iPhone 5 clearly has the ability to be more power efficient on battery. The 5 drops down to iPhone 4 levels of idle power consumption in roughly half the time of the iPhone 4S. Given the same workload that doesn't run indefinitely (or nearly indefinitely), the iPhone 5 will outlast the iPhone 4S on a single charge. Keep the device pegged however and it will die quicker.

Out of curiosity I wanted to toss in a couple of other devices based on NVIDIA and Qualcomm silicon to see how things change. I grabbed both versions of the HTC One X:

The Tegra 3 based One X actually performs very well in this test, but its peak power consumption is significantly worse than everything else. It makes sense given the many ARM Cortex A9 cores built on a 40nm G process running at high clock speeds on the Tegra 3.

The 28nm Snapdragon S4 (dual-core Krait) based One X gives us some very interesting results. Peak power consumption looks identical to the iPhone 5, however Apple is able to go into deeper sleep states than HTC can with its S4 platform. Performance is a little worse here but that could be a combination of SoC and software/browser. I used Chrome for all of the tests so it should be putting Android's best foot forward, but the latest update to Safari in iOS 6 really did boost javascript performance to almost untouchable levels.

At the end of the day, the power profile of the iPhone 5 appears to be very close to that of a modern Snapdragon S4 based Android smartphone. Any battery life gains that Apple sees are strictly as a result of software optimizations that lead to better performance or the ability to push aggressively to lower idle power states (or both). It shouldn't be very surprising that these sound like a lot of the same advantages Apple has when talking about Mac battery life as well. Don't let the CPU cores go to sleep and Apple behaves similarly to other device vendors, but it's really in idle time or periods of lighter usage that Apple is able to make up a lot of ground.

There's one member of the modern mobile SoC market that we haven't looked at thus far: Intel's Medfield. The data below isn't directly comparable to the data above, my measurement methods were a little different but the idea is similar - we're looking at device level power consumption over time while Kraken runs. Here I'm only focusing on the latest and greatest, the Atom based Motorola RAZR i, the Snapdragon S4 based Droid RAZR M and the iPhone 5. The RAZR i/M are nearly identical devices making this the perfect power profile comparison of Atom vs. Snapdragon S4. The RAZR i is also the first Atom Z2460 based part to turbo up to 2.0GHz.

Very interesting. Atom is the only CPU that can complete the Kraken benchmark in less time than Apple's Swift. Peak power consumption is definitely higher than both the Qualcomm and Apple devices, although Intel's philosophy is likely that the added power usage is worth it given the quicker transition to idle. Note that Atom is able to drive to a slightly lower idle level than the Snapdragon S4, although the Swift based iPhone 5 can still go lower.

At least based on this data, it looks like Intel is the closest to offering a real competitor to Apple's own platform from a power efficiency standpoint. We're a couple quarters away from seeing the next generation of mobile SoCs so anything can happen next round, but I can't stress enough that the x86 power myth has been busted at this point.

I will add that despite Intel's performance advantage here, I'm not sure it justifies the additional peak power consumption. The RAZR i ends up being faster than the iPhone 5 but it draws substantially more power in doing so, and the time savings may not necessarily offset that. We'll see what happens when we get to our battery life tests.

 

GPU Analysis/Performance Battery Life
Comments Locked

276 Comments

View All Comments

  • Sufo - Tuesday, October 16, 2012 - link

    Agreed. If his goal is to fly the flag for apple (who clearly need no flag flying - look at their stock prices, but i digress...), and discredit its detractors, he's doing an awful job. But then again, I do detect a whiff of troll.
  • Spunjji - Friday, October 19, 2012 - link

    Word.
  • doobydoo - Saturday, October 20, 2012 - link

    Bragging? About being an engineer?

    LOL
  • dagamer34 - Tuesday, October 16, 2012 - link

    If you wanted a "should I upgrade to this phone" review, there are hundreds of those reviews online. But AnandTech is pretty much the only place where you get a definitive review worth reading 5 years from now. They leave no stone unturned.
  • Arbee - Tuesday, October 16, 2012 - link

    Agreed. "Should I upgrade" is covered by literally dozens of newspapers, TV shows, and websites (Engadget, The Verge, Gizmodo, All Things D just to name 4). AT is the home of the 15+ page deep dive, and they do it just as well for Androids and Windows Phones.

    Also, I'm completely positive that if you sent Brian a GS3 with the iPhone 5's camera he'd write about it in exactly the same way. 2 weeks ago DPReview covered the iPhone 5's camera in a very similar way (including the same suggestions on how to avoid the problem, and a demonstration of inducing similar artifacts on the iPhone 4S and a couple of Android handsets). Optics is not a soft science, there is no room for fanboyism.
  • rarson - Wednesday, October 17, 2012 - link

    I totally disagree. He brings up a completely valid point because Anandtech usually separates the reviews from the in-depth tech examinations. There's absolutely no need for the review to be 20 pages when most people are looking for benchmarks and hands-on impressions. Considering the fact that going this in-depth made the review late, it makes no sense at all.

    At least half of this information in this article doesn't even fall under the category of a review.
  • darkcrayon - Tuesday, October 16, 2012 - link

    I think this type of review (hell, the site in general) is directed at people that want the maximum amount of compiled nitty gritty techy details... Notice his review was weeks after the larger more general consumer oriented sites. I think anyone wanting to know whether they should upgrade, that isn't interested in the technical details of the A6, would be better served reading those reviews anyway.

    Anand has said in previous reviews that he felt that iOS was intended to be more of an "appliance" OS. It's a pretty apt comparison of the two actually. That focus is why you can side load and more easily put custom software on Android, and also why you'll need anti-malware software for it before long as well. The point of an appliance is to have a reliable, consistent device that you spend more time using than tweaking.
  • daar - Wednesday, October 17, 2012 - link

    Point taken, darkcrayon.

    I prefer AT's reviews because they do a thorough and unbiased job at detailing/benchmarking and comparing different products. The suggestion was that the info about the SoC be split on it's own. If Intel released a new chip, call it i9, and the first sample was from an Alienware notebook, I would simply be suggesting that the technical info about the chip have it's own post and not be combined with the review of the notebook is all.

    I find it a bit strange that people are suggesting to go to other websites when I made the comment of comparisons to other products, and quite unlike most posts in AT reviews. If I make a comment about a few ATI features not being compared with Nvidia's, I would have been surprised to have people to tell me to go visit Tom's Hardware or the like.

    Not to say there wasn't any comparisons, but rather in contrast to say, for example, the One X review where Brian made the comment of how the construction of the device felt better than the GS3. It felt like punches were being pulled in this review is all.
  • phillyry - Sunday, October 21, 2012 - link

    Anand,

    I would like to know, however, how an Android device serves more as an all purpose device than an iPhone.

    Did you mean because of its customisable skins or because it can do some things that an iPhone cannot - presumably because of Apple's strong hold ('death grip') on the OS?

    This is pretty important to me because I am near the end of the term of my agreement and am in the market for a new 'phone'. I've considered W8P for precisely this reason but am waiting to see if they flop or not. I've always thought of Android as pretty darn similar to iOS but with slightly different interfaces and less user restrictions.

    Is there some other factor that makes an Android any more like a pocket computer, like the future x86 W8P phones will presumably eventually be, and less like an iPhone than I have imagined?
  • phillyry - Sunday, October 21, 2012 - link

    I also took notice of it when Anand referred to the iPhone as an appliance. Your remark saying, "The point of an appliance is to have a reliable, consistent device that you spend more time using than tweaking" would be comforting but I don't think that that's quite how Anand meant it. I was actually quite put off by the term because I think that he meant that the iPhone is made to be more of a tag along device that goes with your other Macs and plays a support role rather than a stand alone device. He pretty much says as much.

    Like I said, I found this a bit off putting but I think he's just saying how he sees it in terms of the respective companies' product lines and agendas. It actually makes a fair bit of sense. I found that when I got an iPhone it made me want an iPad. And then when I got an iPad it made me want a MacBook. Call it what you will but I remember thinking that they should be able to make it so that I can do everything I need to on an iPad but distinctly felt like I really needed a MacBook to really do all that I wanted. It could be argued, along the lines of Anand's original comment, that this is Apple's approach / business model.

    It also points to a distinction between Apple and the other big player that no one in this forum is talking about - Microsoft. Windows 8 appears to be meant to be the exact opposite of this approach. Instead of one device for each purpose it's one device for all purposes. It will be interesting to see if Microsoft's approach with Windows 8 will turn things around or simply flop, at least on the handheld device side of things.

Log in

Don't have an account? Sign up now