Power Consumption & Noise

The Mac Pro’s thermal core makes a lot of sense from an area efficiency standpoint as the chances that you have all three processors in the system (Xeon CPU + dual AMD FirePro GPUs) running at max speed at the same time is highly unlikely. By having all three players share one large heatsink Apple can optimize for the most likely usage scenarios where at most one processor is running at close to max TDP. From the moment the system was introduced however I was curious to see if its thermal design could deal with all three processors going full tilt. I decided to test both scenarios out.

The vast majority of the time the Mac Pro’s single fan spins at a paltry 769 RPM. At this speed the Mac Pro is virtually silent. I have a Promise Pegasus R6 Thunderbolt chassis with four 3.5” 7200 RPM hard drives inside. The Pegasus sits four feet away from my Mac Pro and at idle the hum of its drives drowns out the idle fan noise of the Mac.

Even running heavily threaded CPU benchmarks does nothing to impact fan speed. It's not until you run a prolonged workload that you can hear an increase in noise from the Mac Pro. I ran FurMark under OS X in parallel with a relatively heavy 4K render in Final Cut Pro. I was rendering a 20 minute 4K project with two effects applied across the entire timeline. The basic render used up 4 - 8 threads, while the effects ensured the compute GPU had some work to do. FurMark obviously kept the display GPU busy. After around 25% of the rendering task was complete the Mac Pro’s fan smoothly scaled up to 1400 RPM, then 1600 RPM and finally stopping at what I believe is full speed: 1900 RPM.

I crudely measured noise sitting at my desk, approximately 18” away from the Mac Pro at all of these points:

Mac Pro (Late 2013) Fan Noise vs. RPM
Fan Speed (RPM) Measured Sound Pressure Level @ 18"
Off 32.2 dBA
770 RPM 32.4 dBA
890 RPM 32.8 dBA
1097 RPM 34.1 dBA
1193 RPM 35.2 dBA
1440 RPM 38.6 dBA
1500 RPM 39.4 dBA
1900 RPM 44.7 dBA

System noise isn’t an issue the vast majority of the time. Even if you’re running for short bursts with everything cranking away on a problem. It’s only under prolonged use of the CPU + both GPUs that the fan has to spin up this high. I quit FurMark and kept the FCP render going, which brought system power down from ~380W to ~326W. It also slowly dropped fan speed from 1900 RPM down to 1500 RPM before smoothly alternating between 1200 RPM and 1450 RPM. The way the Mac Pro’s fan ramps is actually just as important as its ability to remove heat. There are no dramatic increases in speed, just an incredibly smooth curve that the Pro’s fan moves up and down.

The system never gets annoyingly loud, it just varies between silent and calmly reminding you that there’s a large fan inside. Even at full bore the Mac Pro’s fan noise is more pleasant than harsh. It’s not magic, just good system design coupled with the fact that even with a pair of D700s Apple went a bit conservative on GPU speed. Had this been a system capable of pulling 800W at the wall, we’d be having a different discussion about noise.

My next task was to see what actually happens in this worst case scenario. If you’re running all of the parts at full tilt, are any of them going to throttle? I have to work pretty hard to get the fan to spin up under OS X, but in Windows it’s a lot easier since I can just toss a single multi-GPU workload at the problem.

I started out by running LuxMark, an OpenCL workload, on both GPUs as well as a multithreaded 7-Zip benchmark on all of the CPU cores. I monitored both CPU and GPU frequencies. The result was no throttling across the board:

Getting an accurate reading on GPU frequencies from Tahiti based GPUs ends up being harder than I expected, but I saw what Ryan reminded me is typical behavior where the GPUs alternate between their 650MHz base clock and 850MHz max turbo. We don’t have good tools to actually measure their behavior in between unfortunately.

The same was true for the CPU. Even with all 12 cores taxed heavily, I never saw any drops below the CPU’s 2.7GHz base clock.

Next I tried a heavier workload on the CPU: a H.264 video encode. Here I just ran the x264 5.01 benchmark in parallel with the LuxMark workload. Once again, I saw no drop in CPU or GPU clocks although I believe I was approaching the limits of where that would hold true. The system was pulling an average of 410W at that point, with peak power draw at 429W.

If you’re wondering, there was little to no impact on the x264 benchmark from having LuxMark run in the background. The first rendering pass took about a 3% hit, likely due to the CPU not being able to turbo as high/at all, but the second heavily threaded pass was on par with my standalone run without LuxMark in the background. LuxMark on the other hand saw around a 14% reduction in performance, from 2040K samples per second down to 1750K when run in parallel with the x264 test. We’re still talking about two extremely compute intensive tasks, the fact that I can run both with little performance reduction is an example of the sort of performance scaling that’s possible if you leverage all of the compute in the Mac Pro.

So far I wasn’t surprised by the platform’s behavior. The Mac Pro’s thermal core and fan was enough to handle a real world workload without throttling. But what about a power virus? For this I ran a combination of FurMark at 2560 x 1440 and Prime95 (in-place large FFTs) across all GPUs and CPU cores.

The GPUs peaked at 97C, which is pretty much as high as a 28nm Tahiti should ever go. The CPU hit a similar temperature, with most cores hovering around 95C. GPU clocks seemed ok, with both GPUs running between 650 - 850MHz (base - boost). The CPU on the other hand dropped down to 2.1GHz (I even saw a short excursion down to 2GHz). Average power while running this workload was 437W, peaking at 463W before CPU throttling kicked in. If you plot out a graph of power vs. time you can see the CPU throttling kick in during the workload.

I have to stress that I haven’t been able to get this to happen in any normal workload, only what’s effectively a power virus for the GPUs and something quite unrealistic for the CPUs. Either way it shows us the upper limit of what the thermal core can do.

Overall power consumption is down considerably compared to previous generation Mac Pros:

Mac Pro Power Consumption
  Idle Multithreaded CPU Load
Apple Mac Pro (Late 2013/2.7GHz-12C) 85.5W 190.7W (Cinebench 11.5)
Apple Mac Pro (Early 2009/2.93GHz-8C) 125.3W 254W (Cinebench R10)
Apple PowerMac G5 Dual 2.5GHz 120.8W 252.2W (Cinebench R10)

Idle power consumption is down and power efficiency under load is way better than the early 2009 Mac Pro I have here. As far as I can tell, max power consumption for either compute system (CPU alone or dual GPUs alone) is around 300 - 320W. With both subsystems combined you'll get the 437W figure I talked about earlier.

You don't even need a power virus to get there. Running two realistic workloads that are heavy enough won't get you up to the 463W point where I saw throttling, but it'll get you close to the max average power I recorded on the Mac Pro.

Thunderbolt 2 Final Words
Comments Locked

267 Comments

View All Comments

  • Anand Lal Shimpi - Tuesday, December 31, 2013 - link

    Behind the multithreaded curve, the two are almost identical :)
  • Calista - Tuesday, December 31, 2013 - link

    It seem to follow the multithreaded graph perfectly, a tiny bit of a blue graph can be seen in the upper right corner. So it's actually hidden by the second graph.
  • japtor - Tuesday, December 31, 2013 - link

    One thing I keep forgetting to ask since it hasn't been mentioned anywhere, does AirPlay display spanning/mirroring work? I figured it used QSV on the other Macs which this machine doesn't have, so just curious if they just left it out completely.
  • skiboysteve - Tuesday, December 31, 2013 - link

    I wonder if they changed it to AMD hardware encode...
  • Calista - Tuesday, December 31, 2013 - link

    So not really a proper upgrade for anyone owning a Mac Pro from the last few years unless Thunderbolt, faster GPU or a small form factor is needed.

    Anyway, it's an impressive package and it's clear Apple have brought with them a lot of the knowledge they have gained over the years building laptops.
  • Lonyo - Tuesday, December 31, 2013 - link

    Indeed. As was the question with the "super thin" iMac... what's the point?

    It's all very well having a super small computer blah blah, but in this instance, for this type of machine and end user, what's the real benefit?
    The cost has gone up for a base model, performance per dollar has gone down compared to the previous one, there's no ability to upgrade GPUs.
    As soon as you start plugging in Thunderbolt devices, there goes your "sleek looks" etc. Plus it's more expensive to get a Thunderbolt HDD/etc than just stick one inside the case, further increasing costs.

    Yes, it looks nice, and from an engineering standpoint it's very well done, but... is it really the right product for the market?
  • Calista - Wednesday, January 1, 2014 - link

    For anyone not planning on bringing the computer with them from time to time it's certainly not a very practical design. Desktop-space is often more highly valued than floorspace, and lack of upgrade paths are obviously a con.

    But for those with a need to bring a powerful computer with them on a set or similar it's a much more practical solution as compared to the previous design. I think Apple was quite aware what they were doing. A complete field setup with a 27" monitor, the Mac Pro, cables, keyboard and mouse is less than 20 kg. Much more than a laptop for sure, but still a fairly acceptable weight.
  • Lonyo - Wednesday, January 1, 2014 - link

    Wouldn't it make more sense to have TWO designs then? A Mac Pro for people who need portability, and a Mac Pro for standard single location users...?

    I mean, I know Apple tends to be all about deciding what the consumer wants for them and removing choice as much as possible, but sometimes that's not the best way.
  • akdj - Wednesday, January 1, 2014 - link

    Why doesn't this model fit that mold? For the stay at home/office/studio...one can easily AND reasonably tie thunderbolt storage together in a very acceptable and aesthetic way. Whether it be a drive enclosure...set of enclosures, TB docks that are now available adding more USB 3/HDMI/audio/et al I/O....who needs a huge box for slow internal 3.5" HDDs anymore? These PCIe SSDs tear the 2.5" models apart. Inside the 'old' style MP, a 'new' GPU on X16 takes up two slots! Sure doesn't leave much room for your MIDI, PCIe SSD or external pro sound card!
    I'm amazed at how few 'get it' here anymore. Especially after such an exhaustive review. I'm a bit biased as I make my mortgage and have for 22 years doing audio and video production. From hauling reel to reels, vinyl, film and racks of around and lighting gear to rMBPs, iPads (now with fill 64 channel wifi front of house control with Mackie) and this new Pro....I've shaved thousands of pounds from load ins and outs. Same in the camera realm. Working the last seven years with Discovery and it's subsidiaries in Alaska, I can't put into words what this machine means to us. And it's ability to pay itself off many times over just in the course of a year. Exciting times. Hopefully an evolution Win OEMs will consider as well. Shouldn't be any moving parts any longer. Wait and space are ALWAYS an issue. As is the price of power....the advantage of speed, and software developers following suit to unload computational crunching to the GPU
  • nunomoreira10 - Tuesday, December 31, 2013 - link

    Now there just need to be a dual cpu single gpu offer to please everybody.

Log in

Don't have an account? Sign up now