You had said that the GPU is beefy because it can support 5 displays. I am countering that the GPU can only drive 3. You stated 'nuh uh, with USB adapters it is 5!'. Which I countered in turn by stating that if is a USB display adapter then the GPU isn't involved, not even a little bit.
I know how a computer works at a low level (not the lowest level though, don't talk about instructions sets and pipeline depths, that goes right over my head) I know that the CPU feeds the instructions to the GPU, so if you want to argue that the CPU is the one doing most of the work, you could be correct in a sense.
EXCEPT! OS X has had, since day 1, a composited interface that was GPU accelerated. It wasn't until at least Tiger or Leopard that it finally got really good, but it has always been there, in the core of the OS, that the interface would be fully handled by the GPU. Why do you think Apple cut off support for older Macs with old crummy intel graphics? Their GPUs couldn't support the features that Apple needed them to support to provide the experience Apple wanted them to provide.
The rMBP stutters, which is a shame. Whether it is CPU or GPU causing the problem doesn't matter, because as others have pointed out, it is a $2200 (BASE!) machine, which by all accounts should be silky smooth all the time, not just when it feels like it.
GPU composited means the GPU chimes in for certain things that the CPU can't do. It's not like the GPU can ever fully take over for everything.
For instance, the GPU can't render a website. That task has to be done on the CPU. Every time you zoom in a website in Safari, the GPU does the animation, but the rendering is done on the CPU once the animation is over. When you are zoomed in and you try to scroll, the GPU animates what the CPU has rendered, but if it has reached a region that the CPU has not rendered, the CPU will continue to render that region, which causes scrolling to drop framerates. This is most evident in TechCrunch's website, or any website which uses JavaScript to dynamically render contents.
If you don't believe me, open up Activity Monitor, on any Mac, and try to scroll or zoom in Safari on any website, see if CPU usage does not jump up.
And note that I mentioned the EFI bug. That's what would cause a huge drop in performance because it really locks your rMBP to 1.2GHz and never allows the rMBP to scale up. Only an SMC reset will help.
And you can easily lay out 5 AutoCAD or Maya windows on 5 different monitors connected to the rMBP. It's still the 650M rendering everything in those AutoCAD and Maya windows. That's what I meant.
The rMBP is indeed a $2200 computer, and for the most part, it behaves like one. I'm just explaining why it may lag. Most of it has to do more with Apple and less with OSX, but it's not like OSX is completely innocent. I don't want to brag about it... but I have written enough codes for Apple platforms to realize that OSX still has a way to go in terms of optimizations. If you want to bring up an example of good composited interface, try iOS.
But despite the issues, which are admittedly minor, I'd still say the rMBP is worth it. When you are lost in your work, be it coding, image manipulating, AutoCAD, or something else, then you won't care about the slight occasional interface lag at all. That is... unless your workflow consists of you using just Safari and visiting multiple websites. Plus Mountain Lion has tremendously improved on Lion in terms of mitigating the lag.
If nothing else, you're still getting 1920 x 1200 workspace on a 15" MacBook. That alone is more important to me than anything else. Thinner chassis, better screen viewing angle, USB ports to both sides, etc... are just icing on the cake.
I just had to reset SMC now because the fans were screaming and the computer was cold and not doing anything. That's never happened before.
And yes scrolling can be choppy on some sites, forcing the GPU online does not matter so that's not it.
Prior to the EFI update, your rMBP may freeze completely if CPU is taxed beyond a certain point.
After the EFI update, it should stop doing that, but... it may throttle down a lot instead...
We never get the happy end of the stick.
🙁