The CPUs

Like the iMac and MacBook Pro before it, Apple has blessed the MacBook Air with Intel's 32nm Sandy Bridge family of CPUs. Despite being named similarly to the Core i5/i7 in the MacBook Pro, only dual-core Sandy Bridge is offered in the MacBook Air. The cases are simply too small to accommodate any 32nm quad-core parts.

Also NVIDIA is completely out of the picture here. While the previous generation MacBook Air used an NVIDIA chipset with integrated GeForce 320M GPU, Apple is relying entirely on Sandy Bridge's processor graphics this round.

Apple opted for ultra low voltage Sandy Bridge CPUs all with a 17W TDP. The previous generation used a 10W part for the 11 and a 17W part for the 13, but remember those figures didn't include NVIDIA's GeForce 320M which is good for at least another 14W under load, and probably a watt or two with the GPU idle. The 17W SNB parts include memory controller and GPU, leaving only the chipset at 3.4W. Max power consumption is likely lower on the new MBAs, although typical power consumption could be higher as Sandy Bridge cores are significantly faster than the Core 2s used before.

There are three different CPUs Apple offers in the new MacBook Air lineup:

2011 Apple MacBook Air CPU Comparison
1.6GHz Core i5 1.7GHz Core i5 1.8GHz Core i7
Available in 11-inch (default) 13-inch (default) high-end 11-inch (option)
high-end 13-inch (option)
Intel Model Core i5-2467M Core i5-2557M Core i7-2677M
Cores/Threads 2/4 2/4 2/4
Base Clock Speed 1.6GHz 1.7GHz 1.8GHz
Max SC Turbo 2.3GHz 2.7GHz 2.9GHz
Max DC Turbo 2.0GHz 2.4GHz 2.6GHz
L3 Cache 3MB 3MB 4MB
GPU Clock 350MHz / 1.15GHz 350MHz / 1.2GHz 350MHz / 1.2GHz
Quick Sync Yes Yes Yes
AES-NI Yes Yes Yes
VT-x Yes Yes Yes
VT-d No Yes Yes
TDP 17W 17W 17W

All three parts support Hyper Threading and Quick Sync, although the latter remains mostly unused in OS X. The 11 comes with a 1.6GHz part by default while the 13 ships with a 1.7GHz chip. Both can be upgraded to the same 1.8GHz Core i7, a big change from last year's lineup where even the upgraded 11-inch model was slower than the base 13.

Turbo is fully supported at the default Intel ratios (more on confirming this later). This is actually a pretty big deal because it means that for single threaded applications you actually get similar performance to a MacBook Pro. It's only in the thread heavy stuff that the Pro machines will pull away.

The default chips for both systems comes with 3MB of L3 cache. The majority of quad-core parts only have 6MB of L3 and seem to do just fine, so I don't expect that this is too big of a deal. The upgraded 1.8GHz CPU comes with an extra MB of cache.

You'll see this in the performance section but there's just no comparison between the CPUs in the 2011 MacBook Air and what Apple shipped last year. If the MacBook Air wasn't fast enough for your last year, the 2011 models should change that.

Introduction Testing Turbo
POST A COMMENT

115 Comments

View All Comments

  • tipoo - Thursday, July 28, 2011 - link

    I'd like to know too, in fact I think a decibel reading for laptop reviews would be great. Reply
  • solatic - Thursday, July 28, 2011 - link

    "... [It's] easy to imagine a future where laptops become a lot more like the new Air and shift to a couple high bandwidth ports instead of numerous lower bandwidth connections."

    I agree in a sense, but I very much disagree with the manner of your idea.

    Getting rid of low-bandwidth ports on laptops is stupid because these low-bandwidth ports are industry standards. The standard display jack for projectors everywhere, from business rooms to classrooms etc., is VGA. Good old VGA from the 90's which was never displaced by HDMI or DVI despite their ubiquity and technological superiority. Why is irrelevant, but my point is that I can't tell you how many people I've seen with Apple laptops who time and again have asked to borrow my machine with its VGA port because they can't find their VGA dongle or forgot it at home/the office.

    VGA, RJ-45, USB - we don't use these jacks because of how much bandwidth they move but because we know we will encounter devices in the field that will use them.

    What you really want, Anand, is a docking station. Lenovo/IBM has/did made/make them for some time for the Thinkpad line. You come to the office, slide your laptop in, and boom - the docking connector is a high bandwidth connector that connects you to network, display, audio, interface, etc.

    The only real problem with docking stations is that they're either proprietary (the Thinkpad ones) or they're too slow for higher-bandwidth applications (USB docking stations). If you see a future in Thunderbolt docking station-type devices - like the Thunderbolt display - then this is a good thing. The Thunderbolt display can now be used by any Apple computer with a Thunderbolt port - whereas Lenovo has to manufacture different docking stations for the X and T series and these docking stations can't be used with Toshibas, Apples, Dells, etc.

    But to propose getting rid of VGA and RJ-45 ports now is not something I can agree with. Put Thunderbolt on new machines, make Thunderbolt projectors etc., wait for them to saturate the market - and then, only then, does it really make sense to get rid of these slower ports.
    Reply
  • repoman27 - Friday, July 29, 2011 - link

    It certainly makes sense to ditch VGA on a product like the MacBook Air, since a VGA port is too large to physically fit inside it. And it makes sense on all other laptops since most people would rather have 10 more mins of battery life all the time than a VGA port on the odd occasion that they need one. I propose that those who own archaic video devices lacking a digital interface buy a $5 adapter and leave it attached to the device, that way people with modern notebooks can connect to them without issue.

    The lack of a wired Ethernet port on the Airs is also due to its ultra slim profile, but it amazes me how many people I know that have no idea that they can plug their laptops into a wired network and get far better throughput. As long as WiFi offers more bandwidth than most people's ISPs, I think you can kiss that RJ45 port goodbye without upsetting too many folks.
    Reply
  • Wolfpup - Thursday, July 28, 2011 - link

    Great reviews like this are why I love this site. Super thorough and interesting on the tech, and, interesting thoughts on practical stuff too.

    I prefer Windows, but have been wanting a secondary Mac for a while for the heck of it. I'm SUPER torn on what to get...

    The 11.6" almost seems perfect, since I can throw it in my bag with my main notebook and be okay-stick it on my desk without too much issue. But...if I ever actually used it as my primary system, the 13.3" one would be a lot more usable. And at THAT point, the 13.3" Pro is a lot more usable, and at THAT point, the 15.4" Pro isn't much larger, and completely destroys it, and of course could be my main system...

    Sooooo you see my dilemma ;)

    Heh...maybe I should just go with the 11 since I'm not planning on using it as my primary.
    Reply
  • name99 - Thursday, July 28, 2011 - link

    "All three parts support Hyper Threading and Quick Sync, although the latter remains mostly unused in OS X. "

    Quick Sync is used by iChat HD, is it not?

    The other natural client for it would be AirPlay. My guess is that, come iOS5 in September, we will see AirPlay on SNB macs beefed up to be able to stream any content (not just h264) to AirPlay devices by doing the transcode transparently on Quick Sync.

    The third obvious sort of client would be a library that third party apps like HandBrake would get to. What's the currents situation now --- do you need to be root to get to QuickSync or can any app use it?

    My guess is that we are facing the constant problem of new "weird" hardware --- it never comes virtualizable in the first iteration, which means that there is ALWAYS the problem of how to mediate access. And we generally see the same pattern
    (a) A single app that is allowed access.
    (b) Some sort of library that provides its own mechanisms for mediating access.
    (c) The hardware (FINALLY) becomes virtualizable.

    Apple is currently at step (a). Getting to (b) is never completely trivial (in spite of the claims of no-nothings in blog comments), at least if you want to do the job properly. You have to consider questions like --- do you use a reservation model, or do you simply provide notifications when you want to grab the hardware away from a user? How easy is it juggle state and provide something that looks virtualized? etc etc.
    And there are ALWAYS, at least in the first gen, weird hardware interlocks that make life more difficult. I know nothing about QuickSync but I would not be surprised if, for example, using it has implications for using the main GPU, meaning one more thing that has to be balanced in the attempt to make it used more generally.

    Can someone from the Windows world (who understands these issues, and has something more useful to say than "Macs suck") tell us how QuickSync is used in the MS world? Does MS provide a general purpose library, and how does the mediation model for that library work?
    Reply
  • name99 - Thursday, July 28, 2011 - link

    Oops, my bad. The Macbook Airs apparently do not have an HD camera because it can't fit in the available depth of the thin screen. So no iChat HD on these models.

    I think the rest of what I said, especially about AirPlay, still stands.
    Reply
  • rootheday - Friday, July 29, 2011 - link

    The sharing/scheduling of the GPU enginers by multiple client applications on Windows is mediated by the OS as part of the WDDM driver model dating back to Windows Vista - QuickSync is no exception. This means that we are already at c) on your hierarchy on Windows with multiple client applications able to easily share the GPU for encoding.

    Moreover, Intel has a library already for this - see http://software.intel.com/en-us/articles/media/

    The media sdk library provides an API that applications can use to perform encoding and decoding. If run on a system with QuickSync hardware support and drivers, the work is routed to the GPU. If not, the library offers a CPU fall back path. This allows ISVs to write their application once - it will just run faster on Sandybridge systems.

    I don't know enough about Apple OS and graphics driver model to comment on how hard it would be for Apple to get to the same level.
    Reply
  • jvmxtra - Thursday, July 28, 2011 - link

    Thanks for the great review. I throughly enjoyed your review but I feel like one thing is missing.
    In fact, for a laptop review, I really want all the sites to start devoting some time and even creating a method to measure the heat that laptop brings on. We have to create some type of way to measure(benchmark?) the heat index as I feel like how hot laptop gets under certain circumstance is critical factor.

    In fact, I had to trade in my 15 inch mbp since it was just getting too hot.
    Reply
  • tipoo - Thursday, July 28, 2011 - link

    The thermals and power consumption page is a start. Reply
  • name99 - Thursday, July 28, 2011 - link

    "This is what Thunderbolt was meant to do. All we need now is widespread adoption, more accessories and a standard for external GPU form factors."

    AND device manufacturers who are not idiots. In particular, where are the TB hubs?
    The device the market obviously wants is a TB to USB3 hub ---
    two TB ports, four USB3 ports --- and yet we still have not seen this.
    I'm sorry, Sonnet, but this would be VASTLY more useful than your EN and FW800 bridges.

    WTF is going on?
    Reply

Log in

Don't have an account? Sign up now