Driving the Retina Display: A Performance Discussion

As I mentioned earlier, there are quality implications of choosing the higher-than-best resolution options in OS X. At 1680 x 1050 and 1920 x 1200 the screen is drawn with 4x the number of pixels, elements are scaled appropriately, and the result is downscaled to 2880 x 1800. The quality impact is negligible however, especially if you actually need the added real estate. As you’d expect, there is also a performance penalty.

At the default setting, either Intel’s HD 4000 or NVIDIA’s GeForce GT 650M already have to render and display far more pixels than either GPU was ever intended to. At the 1680 and 1920 settings however the GPUs are doing more work than even their high-end desktop counterparts are used to. In writing this article it finally dawned on me exactly what has been happening at Intel over the past few years.

Steve Jobs set a path to bringing high resolution displays to all of Apple’s products, likely beginning several years ago. There was a period of time when Apple kept hiring ex-ATI/AMD Graphics CTOs, first Bob Drebin and then Raja Koduri (although less public, Apple also hired chief CPU architects from AMD and ARM among other companies - but that’s another story for another time). You typically hire smart GPU guys if you’re building a GPU, the alternative is to hire them if you need to be able to work with existing GPU vendors to deliver the performance necessary to fulfill your dreams of GPU dominance.

In 2007 Intel promised to deliver a 10x improvement in integrated graphics performance by 2010:

In 2009 Apple hired Drebin and Koduri.

In 2010 Intel announced that the curve had shifted. Instead of 10x by 2010 the number was now 25x. Intel’s ramp was accelerated, and it stopped providing updates on just how aggressive it would be in the future. Paul Otellini’s keynote from IDF 2010 gave us all a hint of what’s to come (emphasis mine):

But there has been a fundamental shift since 2007. Great graphics performance is required, but it isn't sufficient anymore. If you look at what users are demanding, they are demanding an increasingly good experience, robust experience, across the spectrum of visual computing. Users care about everything they see on the screen, not just 3D graphics. And so delivering a great visual experience requires media performance of all types: in games, in video playback, in video transcoding, in media editing, in 3D graphics, and in display. And Intel is committed to delivering leadership platforms in visual computing, not just in PCs, but across the continuum.

Otellini’s keynote would set the tone for the next few years of Intel’s evolution as a company. Even after this keynote Intel made a lot of adjustments to its roadmap, heavily influenced by Apple. Mobile SoCs got more aggressive on the graphics front as did their desktop/notebook counterparts.

At each IDF I kept hearing about how Apple was the biggest motivator behind Intel’s move into the GPU space, but I never really understood the connection until now. The driving factor wasn’t just the demands of current applications, but rather a dramatic increase in display resolution across the lineup. It’s why Apple has been at the forefront of GPU adoption in its iDevices, and it’s why Apple has been pushing Intel so very hard on the integrated graphics revolution. If there’s any one OEM we can thank for having a significant impact on Intel’s roadmap, it’s Apple. And it’s just getting started.

Sandy Bridge and Ivy Bridge were both good steps for Intel, but Haswell and Broadwell are the designs that Apple truly wanted. As fond as Apple has been of using discrete GPUs in notebooks, it would rather get rid of them if at all possible. For many SKUs Apple has already done so. Haswell and Broadwell will allow Apple to bring integration to even some of the Pro-level notebooks.

To be quite honest, the hardware in the rMBP isn’t enough to deliver a consistently smooth experience across all applications. At 2880 x 1800 most interactions are smooth but things like zooming windows or scrolling on certain web pages is clearly sub-30fps. At the higher scaled resolutions, since the GPU has to render as much as 9.2MP, even UI performance can be sluggish. There’s simply nothing that can be done at this point - Apple is pushing the limits of the hardware we have available today, far beyond what any other OEM has done. Future iterations of the Retina Display MacBook Pro will have faster hardware with embedded DRAM that will help mitigate this problem. But there are other limitations: many elements of screen drawing are still done on the CPU, and as largely serial architectures their ability to scale performance with dramatically higher resolutions is limited.

Some elements of drawing in Safari for example aren’t handled by the GPU. Quickly scrolling up and down on the AnandTech home page will peg one of the four IVB cores in the rMBP at 100%:

The GPU has an easy time with its part of the process but the CPU’s workload is borderline too much for a single core to handle. Throw a more complex website at it and things get bad quickly. Facebook combines a lot of compressed images with text - every single image is decompressed on the CPU before being handed off to the GPU. Combine that with other elements that are processed on the CPU and you get a recipe for choppy scrolling.

To quantify exactly what I was seeing I measured frame rate while scrolling as quickly as possible through my Facebook news feed in Safari on the rMBP as well as my 2011 15-inch High Res MacBook Pro. While last year’s MBP delivered anywhere from 46 - 60 fps during this test, the rMBP hovered around 20 fps (18 - 24 fps was the typical range).


Scrolling in Safari on a 2011, High Res MBP - 51 fps


Scrolling in Safari on the rMBP - 21 fps

Remember at 2880 x 1800 there are simply more pixels to push and more work to be done by both the CPU and the GPU. It’s even worse in those applications that have higher quality assets: the CPU now has to decode images at 4x the resolution of what it’s used to. Future CPUs will take this added workload into account, but it’ll take time to get there.

The good news is Mountain Lion provides some relief. At WWDC Apple mentioned the next version of Safari is ridiculously fast, but it wasn’t specific about why. It turns out that Safari leverages Core Animation in Mountain Lion and more GPU accelerated as a result. Facebook is still a challenge because of the mixture of CPU decoded images and a standard web page, but the experience is a bit better. Repeating the same test as above I measured anywhere from 20 - 30 fps while scrolling through Facebook on ML’s Safari.

Whereas I would consider the rMBP experience under Lion to be borderline unacceptable, everything is significantly better under Mountain Lion. Don’t expect buttery smoothness across the board, you’re still asking a lot of the CPU and GPU, but it’s a lot better.

Achieving Retina Boot Camp Behavior & Software Funniness
POST A COMMENT

470 Comments

View All Comments

  • vision33r - Sunday, June 24, 2012 - link

    When a PC laptop goes on sale, the listed price is never the actual purchase price.

    A $1000 Dell usually end up getting sold for $800 or less after coupons and Dell runs sales all the time. Same goes for HP.

    Apple almost never do a sale until the model is outdated, the only discount is the education one.

    It's a certain that all PC laptop makers have to cut corners to make a profit, competition is fierce. Most buyers are more price sensitive these days then specs.
    Reply
  • duploxxx - Monday, June 25, 2012 - link

    Many manufacturers allow options in there designs towards more cutting edge technology...

    I have a full HD display in a 15"since 2008, same for my SSD.... just a matter of cutting cost for low profile. This differentiate with apple who already put these in the baseline... call bleding edge wathever you want but I am sure my Laptop cost probably a few 100$ less with eluminated keyb, optimus etc.... but it hasbn't got the shiny apple logo :)
    Reply
  • Johnmcl7 - Saturday, June 23, 2012 - link

    Sony have been offering 13.1 1920x1080 screens for a few years which admittedly isn't nearly as high as the new Macbook screen but given Sony have been frequently criticised for offering such a pointlessly high resolution it's little surprise they haven't developed it further.

    When Apple do it however they get praised for their innovation and bringing the market forward when in reality they're a while behind other companies who are genuinely innovative and getting the technology out there.

    John
    Reply
  • Super56K - Saturday, June 23, 2012 - link

    I'm not sure you understand. It's rendered at double the resolution, but presented at the same size as 1440x900 or 1900x1200 on a 15" screen. You gain clarity rather than real estate.

    What other notebooks out there can do that?
    Reply
  • ananduser - Saturday, June 23, 2012 - link

    Lol...you just described DPI scaling. The retina mb just offers ready made presets. To achieve the same effect on the Z simply change the DPI scaling within the native resolution. Reply
  • KoolAidMan1 - Saturday, June 23, 2012 - link

    Scaling in Windows doesn't work the same, nor is it targeted towards such specific resolutions. Anand talks about this himself in the review.

    Hopefully Windows 8 outside of the Metro UI addresses this.
    Reply
  • OCedHrt - Sunday, June 24, 2012 - link

    That's because Windows only goes up to 1.5 instead of 2. But at 1920x1080, 1.5 gives you 1280 x 720. Do you really want to go that small? Reply
  • ananduser - Sunday, June 24, 2012 - link

    OMG...it's been said 10 times already in the comments. Windows goes all the way up to 200%. Anand does not know Windows setting well enough. Reply
  • ananduser - Sunday, June 24, 2012 - link

    That't the idea, scaling should *NOT* be dependent on specific resolutions. It should be agnostic. That's what Windows does because it's supposed to power the world's computers, macs included. Reply
  • dagamer34 - Sunday, June 24, 2012 - link

    Windows 8 addresses this by providing an easy way to serve up high resolution assets for the OS to use depending on the DPI of the machine. It takes all of the guesswork out of the developers hands with no extra code needed. Reply

Log in

Don't have an account? Sign up now