The Mac Pro Review (Late 2013)
by Anand Lal Shimpi on December 31, 2013 3:18 PM ESTPutting Mac Pro Performance in Perspective: Professional Apps
With the legacy Mac Pro comparison out of the way, I wanted to put the Mac Pro's performance in perspective relative to other high-end, modern Macs. I grabbed the 2012 15-inch rMBP, the entry level and upgraded 2013 15-inch rMBPs as well as the new 27-inch Haswell iMac for comparison. I also included my 2009 8-core Mac Pro. I received a reader request to try running the Cycles benchmark in Blender (an open source 3D renderer), so I'll start with that:
Under OS X, this is still a CPU test - the GPUs remain idle and out of the picture here. If you're wondering why the 27-inch iMac doesn't do so hot here, it's because I'm testing the 4 core/4 thread Core i5 version while the rMBPs all have Hyper Threading enabled and are thus 4 core/8 thread configs. The extra logical core per physical core definitely increases architectural utilization/efficiency in this well-threaded test.
Here we have an example where Haswell's IPC improvements don't do a whole lot, which is music to the ears of those considering buying a Mac Pro now vs. when Haswell EP hits in about a year. There's a clear benefit to opting for even the compact Mac Pro over any of Apple's other Macs. The improvement in performance, particularly with the 12-core configuration, is astounding. The Mac Pro completes the rendering work in less than half of the time of the rMBP.
For my next two tests I'm going to be looking at Final Cut Pro 10.1 performance. Given how much Apple is focused on 4K video editing as a usage model for the new Mac Pro, I went out and filmed a bunch of samples in 4K and created a couple of benchmarks to stress the new Mac Pro. As I mentioned earlier, most effects rendering in FCP 10.1 seems to take place on the GPU(s) while everything else seems more CPU bound. For my first test I wanted a project that was lighter on the GPU, so I had a minimal number of effects and no transitions. While the GPU still plays a role (as you'll see below), this should be a good CPU test. I confirmed that portions of the test had no problems keeping all 12 cores/24 hardware threads busy, while others stayed around the 5 - 8 core range.
You'll notice that I have two configurations of the early 2009 Mac Pro listed. One features the machine's stock NVIDIA GeForce GT 120, while the other has been upgraded to Sapphire's Radeon HD 7950 Mac Edition. The only other point I should make is the 2.0GHz 2013 15-inch rMBP configuration features no discrete GPU, it only has Intel's Iris Pro graphics. The 2.3GHz model does feature an NVIDIA GeForce GT 750M GPU.
The first thing I noticed while running this test is how much the workload can impact CPU core utilization. Even though I was dealing with a substantial 4K project, only portions could spawn enough work to keep all 12 cores/24 threads busy. I suspect for video work the optimal cost/performance combination may be the 8-core/3.0GHz part. That being said, it is nice to have a handful of available cores to keep system responsiveness up even while working on rendering a big video project.
I made a point to talk about the GPU configurations before presenting the chart for a good reason: Final Cut Pro 10.1 appears to be incredibly dependent on GPU performance, especially when there's any sort of effects rendering going on. Note that simply moving to a lower clocked Haswell and ditching the discrete GPU causes the 15-inch rMBP to take more than 70% longer to complete this benchmark. I'm not sure how much of this has to do with Intel's graphics drivers just not being optimized for FCP's OpenCL workload, but if you're planning on doing any real work in the latest Final Cut Pro you're going to want a discrete GPU.
The new Mac Pro completed my first FCP 10.1 render test in around half the time of the older 2009 8-core Mac Pro with the upgraded GPU. Without the upgraded GPU, despite this being a very CPU bound test, the older Mac Pro is absolutely destroyed by the new config. The new Mac Pro manages to complete my 4K test in less than 1/6 of the time of the 2009 model without any ugprades.
The next FCP 10.1 benchmark adds in a significant number of effects and transitions to drive up GPU usage. I'm presenting two charts, one without the Iris Pro rMBP and GT 120 Mac Pro and one with them included:
The difference in performance between Intel's Iris Pro graphics and NVIDIA's GeForce GT 750M is staggering. The Iris Pro rMBP15 configuration takes nearly an hour to complete my test, while the dGPU configuration does it in a little over 21 minutes. Here the 27-inch iMac's beefy GPU seems to help make it faster than the rMBP notebooks. The new Mac Pro pulls ahead of the upgraded 2009 model, though not by as much as I would've expected. The second GPU isn't being used as much as it could be it seems. Once again, a standard 2009 model wouldn't fare nearly as well here. Even with a Radeon HD 4870 I bet we'd be seeing significantly lower performance.
The default GT 120 GPU gives us a slight indication of what a slower GPU would do to FCP performance here. What took the new Mac Pro with its dual FirePro D700s under 15 minutes to do, took an hour and 45 minutes to do on the 2009 model with entry level GPU. The same system but with a Sapphire Radeon HD 7950 dropped its render time to 18 minutes.
It is really surprising just how big of an impact GPU performance can have on Final Cut Pro 10.1. It makes total sense that Apple went dual GPUs top to bottom with the new Mac Pro. It seems the latest version of Final Cut Pro was designed with the new Mac Pro in mind, which is unfortunate for anyone who was hoping to get by with an older Mac Pro with a far less capable GPU. It's very clear to me that the Mac Pro is really designed to be an upgrade on all fronts (CPU, GPU, SSD and external IO). The question is how many of those parts have existing Mac Pro users upgraded on their own. The answer to that will ultimately determine how big of a step forward the new Mac Pro really is.
Facebook
Twitter
RSS
267 Comments
View All Comments
Dandu - Friday, January 10, 2014 - link
Hi,It's possible to use a 2 560 x 1 440 HiDPI definition, with a NVIDIA card, a 4K Display and the (next) version of SwitchResX.
I have tested that : http://www.journaldulapin.com/2014/01/10/ultra-144...
Haravikk - Sunday, January 12, 2014 - link
The news about the USB3 ports is a bit strange, doesn't that mean a maximum throughput of 4gbps? I know most USB3 storage devices will struggle to push past 500mb/sec, but that seems pretty badly constrained. Granted, Thunderbolt is the interface that any storage *should* be using, but the choices are still pretty poor for the prices you're paying, and no-one offers Thunderbolt to USB3 cables (only insanely priced hubs with external power).Otherwise the review is great, though it'd be nice to see more on the actual capabilities of Apple's FirePro cards. Specifically, how many of the FirePro specific features do they have such as 30-bit colour output, EDC, ECC cache memory, order-independent-transparency (under OpenGL) and so-on? I'm assuming they do given that they're using the FirePro name, but we really need someone to cover it in-depth to finally put to rest claims that consumer cards would be better ;)
eodeot - Monday, February 24, 2014 - link
I'd love a realistic comparison with an i7 4770k and say, 780ti.You also compare 12 cored version to older 12 core versions that hide behind (fairly) anonymous xeon labeling that hide their chip age (sandy/ ivy bridge/haswell...). I'd like to see in how any real world applications does a 12 core chip perform faster. Excluding 3d work and select video rendering, I doubt there is much need to extra cores. You note how its nice to have buffer of free cores for everyday use, while heavy rendering- but I never noticed a single hiccup or a slowdown with 3d rendering on my i7 4770k with all 8 logical cores taxed to their max. How much of better performance then "butter smooth" one already provided with a much cheaper CPU can you get?
Also you compare non apple computers with same ridiculous CPU/GPU combinations. Who in their right mind would choose a 4core Xeon chip over a haswell i7? The same goes for silly "workstation" GPU over say a Titan. Excluding dated opengl 3d apps, no true modern workstation benefits from a "workstation" GPU, if we exclude select CUDA based 3d renderers like iray and vray rt that can benefit from 12gb of ram. GPUs included with Apple Mac pro have 2gb... Not a single valid reason a sane person would buy such a card. Not one.
Also, you point out how gaming makes the most sense on windows, but do no such recommendation for 3d work. Like games, 3d programs perform significantly better under directX and that leaves windows as a sole option for any serious 3d work...
I found this review interesting for design Apple took, but everything else appears one sided praise...
pls.edu.yourself - Wednesday, February 26, 2014 - link
QUOTE: "The shared heatsink makes a lot of sense once you consider how Apple handles dividing compute/display workloads among all three processors (more on this later)."Can anyone help point me to this. I think one of my GPU's is not being used.
PiMatrix - Saturday, March 8, 2014 - link
Apple Fixed the HiDPI issue on Sharp K321 in OS 10.9.3. Works great. Supported HiDPI resolutions are the native 3840x2160, and HiDPI: 3200x1800, 2560x1440, 1920x1080, and 1280x720. You can also define more resolutions with QuickResX but the above seem to be enough. Using 3200 x1800 looks fantastic on this 4K display. Great job Apple!le_jean - Monday, March 10, 2014 - link
Any information on updated 60Hz compatibility concerning Dell's UP 2414Q in 10.9.3?I would be very interested to get some feedback in relation to:
nMP & Dell UP 2414Q
rMBP & Dell UP 2414Q
I remember in anandtech review of late 2013 nMP there have been issues concerning that specific display, while Sharp and ASUS performed just fine
philipus - Monday, April 14, 2014 - link
As a happy photo amateur, I have to say the previous Mac Pro is good enough for me. I have the early 2008 version which I like because of its expandability. Over the years I have added drives, RAM and most recently a Sonnet Tempo Pro with two Intel 520 in order to get a faster system. As cool and powerful as the new Mac Pro is, it would cost me quite a lot to add Thunderbolt boxes for the drives I currently use, so it is not worth it for me.I do agree that it is about time a manufacturer of desktop computers pushed the platform envelope. It's been tediously samey for a very long time. I'm not surprised it was Apple that made the move - it's in Apple's DNA to be unexpected design-wise. But as much as it is nice to see a radical re-design of the concept of the desktop computer, I think a future version of the Mac Pro needs to be a bit more flexible and allow more user-based changes to the hardware. Even if I could afford the new Mac Pro - and I would also place it on my desktop because it's really pretty - I wouldn't want to have several Thunderbolt boxes milling around with cables variously criss-crossing and dangling from my desk.
walter555999 - Saturday, June 7, 2014 - link
Dear Anand, could you post how to connect a up2414Q to macbook pro retina (2013) ? I have tried a cable mini display port-HDMI. But there are no image in the dell monitor. Thank you very much. WalterFasarinen - Saturday, August 9, 2014 - link
Thanks for an excellent review. (And hello, everybody; this is my first post on this site.)I noticed, in the "GPU choices" section, what seems to be a very useful utility for monitoring the GPU. The title on the top of the screen is "OpenCL Driver Monitor"; the individual windows (which are displaying graphs of GPU utilisation) seem to be titled "AMDRadeonXL4000OpenCLDriver".
I'm probably just being dim, but a bit of googling doesn't shed much light. If anybody could point to me to where this utility can be obtained from, I'd be most grateful.
Thanks ....
pen-helm - Friday, September 12, 2014 - link
I showed this page to a Mac user. They replied:I'm pretty sure that this simple fix takes care of the issue with
monitors where OS X doesn't offer a HiDPI mode:
http://cocoamanifest.net/articles/2013/01/turn-on-...