With the exception of article production or live blogging, my on-the-road notebook usage model is filled with tons of idle time. Last week I was in a large conference room, sitting through presentations from 9AM - 5PM every day. There was an hour break for lunch, and a couple of 15 minute breaks spread throughout, but for the most part I had my notebook open, taking notes and occasionally pulling up websites to reference/research after having a thought.

My in-meeting notebook usage is actually a lot like what my notebook usage was as a student in college. Very light web browsing (unless I really didn’t have to pay attention), coupled with background IM, email and tons of note taking. I have a feeling this usage model isn’t all that unique to me. On the contrary, I bet it’s quite common. Which makes this next part hilarious: notebook PCs actually did a terrible job of running this very scenario.

Power efficiency was always a problem. The only notebooks you wanted to carry around with you were the ones that had tiny batteries. The larger notebooks had big batteries but also had big screens and power hungry components. We used to have a battery life test that simply measured how long it would take a notebook to die if we left it idling at the windows desktop. Just two years ago, it wasn’t unusual to see notebooks incapable of breaking 5 hours of idle battery life.

The truth is that it wasn’t just display quality, terrible track pads and sluggish mechanical hard drives that drove people to tablets. Great platform idle power coupled with very efficient mobile OSes really made the current tablet revolution possible.

Back in the early 2000s, Matthew Witheiler (our first graphics editor) was on a tablet PC kick. He searched high and low for anyone who’d bring a tablet to market. In college at the time, I understood why he wanted a tablet. The experience fell short at the very same points every time. Tablets back then were too big, too slow and had terrible battery life. The PaceBook PaceBlade lasted under 3 hours on a single charge back when we reviewed it in 2002. It also took 11 seconds to wake up from standby, and 84 seconds to boot (the Transmeta Crusoe TM5600 inside was slower than a 433MHz Celeron at the time).

The current crop of ARM based tablets largely fixed this problem. They aren’t all that quick if you compare to modern high-end CPU and GPU architectures, but they benefit from much lighter weight apps and OSes that are more efficient.

When Intel first started talking about Haswell and Ultrabooks, it did so under the banner of fixing the “ARM problem” and merging the best of tablets and notebook PCs. Looking around at the first implementation of Haswell ULT and the Ultrabooks based on it, they just look like better versions of the systems that came before them. Haswell ULT definitely posts better battery life than any previous Intel Core microarchitecture, but everything the world did with it seemed so very...predictable. Even Apple just slotted Haswell ULT into the same chassis as Sandy Bridge and Ivy Bridge ULV.

The idea for this article struck me as I was in meetings last month. Sitting in that conference room for 8 hours straight each day would’ve killed my rMBP13 without plugging it in. The 2013 MacBook Air on the other hand did just fine. At one point there was some drama around a few power outlets not working. Much like using a tablet, I didn’t care. Even when I had only 50% of my battery charged, I had more than enough juice to get through the day without hunting for a power outlet. Given a very light usage model, Haswell ULT behaved like an ARM tablet platform. The difference being that if/when I needed more performance, it was available.

This whole situation convinced me to run a test that a few AnandTech readers had asked me for a few weeks ago: run our tablet battery life workload on the 2013 MacBook Air. Even our lightest Mac battery life workload is still heavier than what we run on smartphones/tablets, so the light workload battery life numbers aren’t really representative of a tablet usage model with Haswell ULT. Luckily our tablet battery life tests are fairly portable, so I prepped the 2013 13-inch MBA the same way I would one of our tablets: brightness calibrated to 200 nits running the very same workload as what we would on a tablet. You’ll notice two bars for the 2013 MacBook Air, one indicating its result and one with that result scaled down to simulate what would happen if it had 78.7% of its actual battery capacity - putting it on equal footing to the 42.5Wh iPad 4. With workload and performance constant, it’s safe to assume that battery life scales linearly at best with battery capacity. In other words, our MacBook Air numbers at 42.5Wh should be indicative of what we’d expect if the 13-inch MBA actually had a 42.5Wh battery rather than 54Wh unit.

First off, our WiFi web browsing test:

We regularly load web pages at a fixed interval until the battery dies (all displays are calibrated to 200 nits as always). The differences between this test and our previous one boil down to the amount of network activity and CPU load.

On the network side, we've done a lot more to prevent aggressive browser caching of our web pages. Some caching is important otherwise you end up with a baseband/WiFi test, but it's clear what we had previously wasn't working. Brian made sure that despite the increased network load, the baseband/WiFi still have the opportunity to enter their idle states during the course of the benchmark.

We also increased CPU workload along two vectors: we decreased pause time between web page loads and we shifted to full desktop web pages, some of which are very js heavy. The end result is a CPU usage profile that mimics constant, heavy usage beyond just web browsing. Everything you do on your device ends up causing CPU usage peaks - opening applications, navigating around the OS and of course using apps themselves. Our 5th generation web browsing battery life test should map well to more types of mobile usage, not just idle content consumption of data from web pages.

Tablet Web Browsing Battery Life (WiFi)

This is what I hinted at during Podcast #21: total platform power of the 2013 13-inch MacBook Air is lower than Apple’s 4th generation iPad. Even if you take into account battery capacity, the 13-inch MBA lasts around 18% longer on a single charge.

What we aren’t taking into account however are the different display panels. The MacBook Air uses a 13.3-inch 1440 x 900 panel, compared to a 9.7-inch 2048 x 1536 panel on the 4th gen iPad. I’m not sure how big of a difference the delta would make. DisplayMate measured 7W for the 3rd gen iPad’s backlight, compared to 2.7W for the iPad 2. If we assume the delta is around 4.2W, that’s roughly another 10% hit that the Haswell ULT platform would have to take in order to bring its display power consumption in line with the iPad. With an 18% advantage in battery life in this test, it looks like even moving to a similar panel would deliver equal if not slightly better platform power consumption for Haswell ULT. Similarly, deploying Haswell ULX instead (lower TDP/SDP version of Haswell) could drive battery life even higher.

Tablets are very often used for video playback, so this next test is just as important as a more interactive workload:

Tablet Video Playback Battery Life

Here I'm playing a 4Mbps H.264 High Profile 720p rip I made of the Harry Potter 8 Blu-ray. The full movie plays through and is looped until the battery dies. Once again, the displays are calibrated to 200 nits.

The video playback results show exactly where Intel needs to focus on improving power efficiency. Granted I’m using QuickTime here, which I can only assume offloads video decode to Intel’s video engine. The video playback story looks better than it did on Microsoft’s Surface Pro, but it’s still not great at all. Modern ARM based SoCs have extremely low power video decoders integrated into the silicon. I wonder if Haswell’s video decode engine just isn’t as low power as what you can get in most ultra mobile SoCs today. Intel’s public documentation tends to focus on transcoding power efficiency relative to software based encode/decode, but not decode power efficiency alone.

What This Means

With Haswell ULT, Intel finally got its platform power story in order. Haswell ULT and, eventually, Haswell ULX platforms appear to have idle power characteristics that are at least within the range of high-end ARM based tablets. It’s finally possible to use Core in a tablet (the thermal considerations can be negated by going with a Y-series or even lower power SKU). Video decode power consumption remains a question in my mind. Assuming the results I saw weren’t due to software, I’d be willing to bet that video decode power efficiency becomes a target for improvement in Broadwell and/or Skylake.


Microsoft Surface Pro (left) vs. 4th gen iPad (right)

There are obvious implications for the next-generation of Microsoft’s Surface Pro. It’s unclear whether Microsoft will wait until Broadwell to reduce the thickness of Surface Pro, or if it’ll go with a Y-series Haswell ULX part this year and release something that’s much thinner immediately. The challenges Microsoft would face there are similar to those Apple faced with the 2013 MacBook Air, namely Microsoft would have to be accepting of a CPU performance regression but a significant improvement in battery life (and form factor). Broadwell should deliver (some of) the best of both worlds, but that’s another year/generation of waiting for Microsoft.

What about Apple? I am not convinced that Apple would leave the intersection of iPad and MacBook Air alone. Tablets are under heavy pricing pressure, and Apple itself has established upper bounds to iPad pricing. As the world continues to shift towards tablets and lower cost/margin computing devices, Apple needs a solution to keep ASPs high. With iPad sales shifting to the mini, a higher end convergence solution between (replacing?) the iPad and 11-inch MBA might not be a bad idea.

At this year’s WWDC, Apple made it very clear that idle power optimizations were high on the list for OS X Mavericks. Reducing the number of CPU cycles used by active but visually occluded application windows, and putting idle applications in a nap mode. These optimizations obviously benefit the Mac notebook lineup, but they’re also very important should Apple try to build a Surface Pro competitor.

The platform could run OS X with a modified launchpad in tablet mode, or the standard OS X desktop in docked mode. Perhaps I’m just projecting Windows 8/Surface onto Apple, but I feel like the possibility is there.

Final Words

If you look at the first Haswell ULT systems, they generally don’t appear all that different from the Ivy Bridge ULV systems that came before them. The biggest change is a tremendous increase in battery life, due to idle power platform optimizations, but in terms of functionality they’re largely unchanged. This brings two thoughts to mind:

The first is that Haswell ULT will ultimately do nothing to change the current trajectory of the PC industry. The problem isn’t in the silicon (for the most part), but rather in the traditional implementation of the silicon by Intel’s OEM partners. From Apple to the army of Ultrabook OEMs, Haswell ULT has only been used to enable good ultraportable notebooks and nothing more exotic. Companies invested in a return to growth in the PC industry won’t find it as a result of Haswell ULT. The question you should be asking instead is how much worse would things have been had Haswell ULT not been as good as it is.

The second is that the best has yet to come. I have high hopes for the second generation of Microsoft’s Surface Pro. Microsoft could build the second generation into a true convergence device that further blurs the lines between tablet and productivity notebook. For the first time in quite a while Microsoft could have a product that shows significant improvement year over year, for multiple years in a row. The first Surface Pro was good, a Haswell ULT/ULX based device could really make the experience more tablet-like and a Broadwell ULT/ULX successor could make it even thinner.

The next few generations won’t be a walk in the park for Intel however. There’s a ton of catching up to do. Just because Intel now has a single-chip Haswell SoC solution doesn’t mean that Intel and the ARM ecosystem are at parity in terms of capabilities. Qualcomm is quick to point out that the CPU island in its Snapdragon SoCs can be around 15% of the total die area, the rest of the SoC being devoted to GPU, ISP, video encode/decode, connectivity, etc... While I don’t expect a high-end Core based SoC to be only 15% CPU cores, I do expect that Intel will need to integrate similarly high-quality, high-performance and low power IP blocks in its flagship silicon. At this point all we’ve established is that on a largely CPU driven workload that Haswell ULT can be competitive (from a power efficiency standpoint) with a high-end ARM based SoC. The video playback results alone point out there’s so much more to the story that matters.

The OS vendors have to similarly make sure they're adequately prepared for this transition. The name of the game is making all usage appear as idle as possible. We've seen improvements along this front in Windows 8, and promised in OS X Mavericks. To blur the lines between tablet and notebook hardware, you need to do the same between tablet and notebook OSes.

Intel prepping its Core family of microarchitectures for low power tablet duty matters quite a bit to notebook OEMs. I don’t believe the computing world will top out at $499, but I do believe that any solution above $499 will have to be something more unique than just a really thin notebook. In my Surface Pro review I talked about that device being a tablet that could serve as a notebook, or as a desktop when docked to a large display/kb/mouse. I’m not much of a visionary, but I feel like such a flexible device might not be a bad idea.

Comments Locked

83 Comments

View All Comments

  • jemima puddle-duck - Monday, July 22, 2013 - link

    This. Thank you for bringing some reality back to this discussion. Can we please have at least a little acknowledgement of costs amongst the technology. It's all very well that the new Ferrari has the efficiency of a Prius, but if it costs 100x more, it's academic to normal people.
  • Ktracho - Monday, July 22, 2013 - link

    I think this is exactly why Microsoft says they aren't giving up on Windows RT. If they can get the number of apps up dramatically (say, by a factor of 1000), and simultaneously find a way to decrease price by, say, half, they could have a winner.

    For those times when performance is not enough, these tablets can be docked, and in the future (this is not yet a reality), people will be able to remote into a powerful PC complete with a real, physical graphics card, and use it as if it were all built into the tablet. I think this is eventually where everyone is headed. In other words, no one will ever need to carry around anything more powerful than a Windows RT system. (If you don't like Windows, Apple will do the same thing with their ecosystem, and Google likewise, etc.) Intel Core CPUs will be relegated almost exclusively to servers, where price does not have to be bargain basement level.
  • DanNeely - Monday, July 22, 2013 - link

    MS currently has 100k apps in the W8 store, vs 600k for Google, and 900k for Apple. More apps wouldn't hurt; but they're much closer to parity than your factor of 1000 implies.
  • Ktracho - Tuesday, July 23, 2013 - link

    I don't really know how many Windows RT apps are in the store, but I doubt there are anywhere near 100K of them.
  • smartypnt4 - Monday, July 22, 2013 - link

    I think this scares Intel more than they're willing to admit. Apple is a very large customer that pays for the best binned CPUs Intel makes (in terms of leakage, not pure GHz). That's 10% of Intel's consumer business right there, which is definitely non-trivial. Apple's already got the people with the expertise to make a quad-core Swift. I think the issue is that it's just flat out too slow to use on OSX and keep a good user experience. Also, Apple would have to do *everything* Intel does associated with the Haswell SoC: a full-sized memory controller (you can't just grab the one from the A6X), and all the I/O (SATA, PCIe, USB, etc.), and that's a non-trivial task.
  • madmilk - Monday, July 22, 2013 - link

    Apple would also cajole a lot of OS X developers into recompiling/porting their application, or else they'll end up with a fruity version of Windows RT.
  • smartypnt4 - Monday, July 22, 2013 - link

    That's very true as well. While it's still a threat to Intel, it's not *that* big a threat, I suppose. That's a lot of legwork that Apple would have to do. I'm not even sure it'd be any cheaper for them to develop, validate, and get their own chip fabbed.
  • psychobriggsy - Tuesday, July 23, 2013 - link

    I don't think Apple will switch to ARM in the near future for their MacBooks, iMacs, etc.

    But *if* they were, they could invest in a larger SoC than they budget for the iPad, and it would be a 64-bit ARMv8 design, not the current ARMv7 Swift. They probably have this core designed, possibly ready to manufacture, maybe even being manufactured in SoCs right now (but more likely for next year's SoCs).

    A quad-core, 20/28nm, 2GHz+ custom ARMv8 SoC should compete fairly well with a ~1.5GHz dual-core with HT Haswell, on the tasks a person wants to run on an 11.6" MacBook Air. The MBA has more thermal headroom than a tablet, so the CPU and GPU upper clock speeds can be higher as well. They might even do a big.LITTLE thing with their own core and an ARM Cortex A7/A53 for the mostly idling common case.

    As for recompiling Mac OS X apps - that's a button press away for the developers, once Apple makes XCode support ARM compilation for desktop apps. Again, in-house I bet this is already happening.

    This path could cost Apple $50 per SoC to manufacture (more advanced process, larger SoC), but that's still vastly cheaper than the price of Haswell, even with the discounts that Apple no doubt gets.
  • djscrew - Monday, July 22, 2013 - link

    You complain about CPU price and then suggest buying an over-marked up Apple product instead? Are you demented? Just get the iPad you're in denial about wanting and move on. Or use the iPad you already probably have and be happy. Either way, if you have an iPad you should donate that extra money to an orphanage or something useful. Besides, everyone knows that no $30 ARM chip can do what a $350 Intel chip can do or Apple would use it. People still want the ability to work on their Airs. Granted in 10 years this all should be pointless as the $30 chips should end up replacing the $350 chips of today and mobile technology + the internet is ubiquitous... that is if we're not all too greedy to realize that goal.
  • beginner99 - Tuesday, July 23, 2013 - link

    Apple does not pay list price for Intel CPUs. I have no idea about the actual price but a safe guess is probably half, eg. $175. No the picture already looks very different. And don't forget that apple still is fancy in content creation stuff which all does require powerful hardware so ARM is already a no go.

Log in

Don't have an account? Sign up now