Absolutely Insane Battery Life

With Haswell ULT, Intel aggressively focused on driving down total platform power consumption. It turns out that although Intel did a wonderful job of driving down CPU power consumption over the years, it did nothing to make the rest of the platform keep up. With Haswell ULT, all of that changed. Intel is being frustratingly cagey with giving up real details on exactly what’s going on with Haswell ULT, but here’s what I’ve been able to piece together.

For starters, Haswell ULT brings the PCH (Platform Controller Hub) on-package. The PCH is responsible for all SATA, USB, PCIe 2.0 and other rest-of-system interfaces. Bringing it on package reduces the amount of power needed to drive traffic between the CPU and PCH, which in turn helps reduce platform power.

The PCH also moves down to 32nm, helping further reduce power consumption. Haswell ULT silicon itself is binned for lower voltage/power operation. The combination of Haswell ULT CPU and PCH are both included in the new 15W TDP (there’s a 28W version as well but not used in the MacBook Air).

Haswell ULT supports lower power sleep states (up to C10) than the standard mobile or desktop parts (C6/C7).


Image Courtesy iFixit

The other big change, and one that Apple is among the first (only?) to take advantage of is Haswell ULT’s support for LPDDR3. Standard DDR3 operates at 1.5V, while low-voltage DDR3L drops that down to 1.35V - the two standards are otherwise identical. LPDDR3 on the other hand drops voltage even further (1.2V) while introducing architectural features to drive power down even lower. LPDDR3‘s power advantage is why it’s frequently used in smartphones vs. DDR3L. The biggest downside is cost. Apple has historically not had an issue with spending a bit extra to get a better overall experience, so it’s not surprising to see the MacBook Air ship with LPDDR3.

Overall bandwidth remains unchanged despite the move to very low power memory. We’re still dealing with a 128-bit wide memory interface with a 1600MHz datarate. Note the impact this has on DRAM device layout on the PCB itself. Last year's model required 16 DDR3L devices, compared to 4 x 32-bit LPDDR3 devices here. Anyone else smell laptop/tablet convergence coming this way?

Haswell ULT also enables support for Intel’s Power Optimizer framework. I’ve talked about this extensively over the past several months, but it’s effectively a messaging system that allows all devices/controllers within a system to coordinate going into sleep states during periods of idle time. Of all of the platform power optimizations, this is the only one that isn’t currently taken advantage of in OS X. You’ll have to wait for OS X Mavericks to realize these gains.

Apple also boosted overall battery capacity on the MacBook Airs by roughly 8%. The increase in battery capacity had no impact on weight. Although it’s not immediately apparent, I would assume that Apple’s new SSDs also support DevSleep (DEVSLP) and Runtime D3.

The result of all of this is a downright tremendous improvement in battery life. OS X already did very well in the idle power department. Haswell’s FIVR (Fully Integrated Voltage Regulator) can more quickly/aggressively enter and exit low power states. The combination of which is really the perfect storm for increasing battery life.

On the 13-inch MBA, Apple claims up to 12 hours of usage on a single charge.

Apple even revised its own testing in order to make its quoted battery life numbers more realistic. Previously it ran all of its own battery life tests at 50% brightness, but starting with the MacBook Air Apple’s quoted battery life numbers are at 75% brightness. Our tests by comparison are at 81.5% (200 nits on the MBA). Apple’s changes to its battery testing methodology actually tend to unintentionally mirror ours. Our first Mac battery life tests ran at roughly 50% brightness (100 nits).

So how did the MacBook Air fare in our testing? To find out I turned to our updated 2012 battery life test suite, first introduced with the 15-inch rMBP review.

The light and medium suites are inherently related - they use the same workload and simply vary the aggressiveness of that workload. The light test hits four different websites every minute, pausing for nearly the entire time to simulate reading time. Flash is enabled and present on three of the sites. The long pause time between page loads is what really makes this a light test. Web browsing may be the medium for the test but if all you’re doing is typing, watching Twitter update and maybe lazily doing some other content consumption this is a good representation of the battery life you’ll see. It’s a great way of estimating battery life if you’re going to be using your notebook as a glorified typewriter (likely a conservative estimate for that usage model).

The medium test hits the same webpages (Flash and all) but far more aggressively. Here there’s less than 10 seconds of reading time before going onto the next page. It sounds like a small change but the impact on battery life is tremendous.

Both the light and medium tests are run in their default state with processor graphics enabled, as well as with the discrete GPU forced on. I run with the dGPU on as well because it’s far too often that a single application open in the background will fire up the dGPU and contribute to draining your battery. The goal here is to deliver useful numbers after all.

The final test is very similar to our old heavy multitasking battery life tests, but with some updates. Here I’m downloading large files at a constant 1MB/s from a dedicated server, while playing back a looped 1080p H.264 movie (the Skyfall trailer) all while running the medium battery life test. The end result is a workload that gives you a good idea of what a heavy multitasking usage model will do in terms of battery life. I’ve found that OS X tends to fire up the dGPU anyway while running this workload so I saw no reason to run a separate set of numbers for processor and discrete graphics.

Light Workload Battery Life

This is just ridiculous. Apple claims 12 hours, we tend to test a little more strenuous than Apple does and ended up with just over 11 hours of battery life on a single charge. These highly idle cases end up dominated by display power, which is why we actually see the smallest improvement in battery life over the previous generation here (~35%, normalized for battery capacity). If you drop brightness down to something more reasonable (~100 nits) you’ll get some truly insane numbers:

I remember owning a Transmeta Crusoe based Sony Picturebook (C1VN) with an extended battery and being able to break 14 hours of battery life. I had to give up so much performance and usability to get that sort of battery life back then; with the new MacBook Air, I don’t have to.

Now this is really the sort of battery life you can expect when using the 13-inch MBA as a glorified typewriter. What happens if you start using the system a bit more aggressively?

Medium Workload Battery Life

Just under 9 hours on a single charge, an increase of 54.5% when you normalize for battery capacity. What the world would’ve done if Haswell ULT hit prior to the creation of the iPad...

The reason I create/present three different battery life tests is to showcase a range of expected battery life. No one number is going to characterize what you can expect out of the system, but my hope is you’ll get a good idea of range by looking at the numbers here. The heavy test used to provide a good look at worst case scenario, but I’m beginning to wonder if I need something even more stressful:

Heavy Workload Battery Life

Even normalizing for battery capacity changes, the new 13-inch MacBook Air increases battery life by 65% over the previous model.

Under really heavy use (think tons of video/photo editing work) you can go even lower than what our heavy workload numbers show. In my experience I found that around 7 hours of battery life on a single charge is reasonable for most of my workloads, but when doing a lot of work (tons of Flash tabs open, compiling a project in the background and heavy multitasking) I could kill the 13-inch MBA in under 4 hours.

The benefit of the new MBA is really in its ability to extend its battery life when needed. Close Safari windows, turn down the brightness, and you’ve got a machine that can last for a very long time without needing a wall outlet. There's a good reason that OS X Mavericks focuses so much on putting background tasks/apps to sleep, maximizing idle time is really the key to getting this insane amount of battery life.

 

More GPU Performance Numbers A Custom Form Factor PCIe SSD
Comments Locked

233 Comments

View All Comments

  • seapeople - Tuesday, June 25, 2013 - link

    Brightness is pretty much the number one power consumer in a laptop like this (which is actually mentioned in the review). If you expect to run anything at 100% brightness and get anywhere near ideal battery life then you are bound to be disappointed.
  • name99 - Monday, June 24, 2013 - link

    "802.11ac ... better spatial efficiency within those channels (256QAM vs. 64QAM in 802.11n). Today, that means a doubling of channel bandwidth and a 4x increase in data encoded on a carrier"

    This is a deeply flawed statement in two ways.

    (a) The modulation form describes (essentially) how many bits can be packed into a single up/down segment of a sinusoid wave form, ie how many bits/Hz. It is constrained by the amount of noise in the channel (ie the signal to noise ratio) which smeers different amplitudes together so that you can't tell them apart.
    It can be improved somewhat over 802.11n performance by using a better error correcting code (which essentially distributes the random noise level over a number of bits, so that a single large amount of noise rather than destroying that bit information gets spread into a smaller amount of noise over multiple bits).
    802.11ac uses LDPC, a better error correcting code, which allows it to use more aggressive modulation.

    Point is, in all this the improved modulation has nothing to do with spatial encoding and spatial efficiency.

    (b) The QAM64 and QAM256 refer to the number of possible states encoded per bit, not in any way to the number of bits encoded. So QAM64 encodes 6 bits per Hz, QAM256 encodes 8 bits per Hz. the improvement is 8/6=1.33 which is nice, but is not "a 4x increase in data encoded on a carrier".

    We are close to the end of the line with fancy modulation. From now on out, pretty much all the heavy lifting comes from
    (1) wider spectrum (see the 80 and 160MHz of 802.11ac) and
    (2) smaller, more densely distributed base stations.
    We could move from 3 up to 4 spatial streams (perhaps using polarization to help out) but that's tough to push further without much larger antennas (and a rapidly growing computational budget).

    There is one BIG space for a one-time 2x improvement, namely tossing the 802.11 distributed MAC, which wastes half the time waiting randomly for one party or another to talk, and switching to a centrally controlled MAC (like the telcos) along with a very narrow RACH (random access channel) for lightweight tasks like paging and joining.
    My guess/hope is that the successor to 802.11ac will consist primarily of the two issues I've described above (and so will look a lot more like new SW than new DSP algorithms), namely a central arbiter for a network along with the idea that, from the start, the network will consist of multiple small low-power cells working together, about one per room, rather than a single base station trying to reach out to 100 yards or more.
  • bittwiddler - Monday, June 24, 2013 - link

    • The keyboard key size and spacing is the same on the 11 and 13" MBAs.
    • The 11" MBA is exempt from being removed from luggage during TSA screenings, unlike the 13.
    • The 11" screen is lower height than most and doesn't get caught by the clip for the airplane seat tray table.
    • When it comes to business travel computing, I'm not interested in a race to the bottom.
  • Sabresiberian - Monday, June 24, 2013 - link

    One thing I would NOT like is for Apple to make a move to a 16:9 screen. I'd certainly rather have 1440x900 on a 13" screen than anything denser that was 16:9. I mean, I'm one of the guys that has been harping on pixel density and refresh rates since before we had modern smart phones (the move to LCDs set us back a decade or more in that regard), but on a screen smaller than 27", 16:9 is just bad. In my not-so-humble opinion.

    4:3 is better for something smaller than 17", but I can live with 16:10. :)
  • Kevin G - Monday, June 24, 2013 - link

    Re-reading trough the review I have a question about the display: does it use panel self refresh? I recall Intel hyping up this technology several years ago and the Haswell slides in this review indicate support for it. The question is, does Apple take advantage of it?
  • Kevin G - Monday, June 24, 2013 - link

    I think that I can answer my own question. I couldn't find the data sheet for the review panel LSN133BT01A02 but references on the web point towards an early 2012 release for it. Thus it looks like it appeared on the market before panel self refresh was slated for wide spread introduction alongside Haswell.
  • hobagman - Monday, June 24, 2013 - link

    Hi Anand & all -- could I ask a more CPU related question I've been wondering about a lot -- how come the die shots always look so colorful and diverse, when isn't the top layer all just interconnects? Or are the die shots actually taken before they do the interconnects, consisting in the top 10-15 layers? Would really appreciate an explanation of this ...
  • hobagman - Monday, June 24, 2013 - link

    I mean, what are we actually seeing when we look at the die shot? Are those all different transistor regions, and if so, we must be looking at the bottom layers. Or is it that the interconnects in the different regions look different ... or ... ?
  • SkylerSaleh - Tuesday, June 25, 2013 - link

    When making the ASIC, thin layers of glass are grown on the silicon, etched, and filled with metal to build the interconnects. This leaves small sharp geometric shapes in the glass, which reacts with the light similarly to how a prism would, causing the wafer to appear colorful.
  • cbrownx88 - Monday, June 24, 2013 - link

    Please please please revisit with the i7 config - been wanting to make a purchase but have been waiting for this review (and now waiting on the update lol).

Log in

Don't have an account? Sign up now