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

  • FunBunny2 - Tuesday, December 31, 2013 - link

    Has everybody forgotten? This is just a Cube with one round corner. I suppose Tim will claim that's been patented too.
  • newrigel - Wednesday, March 1, 2017 - link

    Right.... with a unified core in it he he.... Mac's rule
  • Y0ssar1an22 - Tuesday, December 31, 2013 - link

    Off the Mac Pro topic but how come the 2013 13" rMBP scores significantly lower than the 2012 and various MBAs in the Cinebench 11.5? I'm personally interested as I have one on order :-) It scores better in later tests (so presumably not a typo?) Cinebench caught my eye as the first cross-benchmark in the review.

    Thanks for this review, and looking forward to the rMBPs in depth!

  • iwod - Tuesday, December 31, 2013 - link

    1. What are the likely chances of a Mac that does Desktop Class Gfx card with 2 x8 PCI-E and uses Desktop Haswell instead. Unless i miss anything surely this is a simple change in production line.
    2. SSD speed is slow, for a Peak rate of 2GB/s, it seems Apple firmware or Samsung Controller not capable of feeling up the peak bandwidth? So which is likely the cause?
    3. GFx ECC Ram. How much of a problem is it? For Professional market? And why Apple decide to ditch this since the price difference are minor for the price of Mac Pro.
  • dwade123 - Tuesday, December 31, 2013 - link

    Who the **** put a trashcan here!?
  • e375ued - Wednesday, January 1, 2014 - link

    Is there some convenient reason Anand let the Mac Pro off easy by using Prime95 instead of Intel Burn Test or linpack?
  • Ryan Smith - Wednesday, January 1, 2014 - link

    It was my suggestion to try maxing out the Mac Pro, just to see if it would throttle (and if so, by how much). I picked Prime95 because it's good enough; not that there's anything wrong with IBT or Linpack, but all 3 of those are close enough that it shouldn't matter (and P95 is easy to use).
  • jrs77 - Wednesday, January 1, 2014 - link

    Good test that shows that the thermal core design works like a charm, even when applying very heavy and rather unrealistic loads to the system.

    Most people will run these new Mac Pros with only having a scene rendered or a video-filter applied etc and in this case the system is basically dead-silent and street-noise totally drowns the noise of the fan anyways.

    Just a tad too expensive for me tho.
  • Kevin G - Wednesday, January 1, 2014 - link

    The ‘mid range’ config is a far better value on the 2012 model since it is a 12 core model. The $200 savings can be put toward a better GPU.

    With regard to Cinebench, does it use AVX under OS X? I suspect that it does and that is where the majority of the single threaded CPU performance increase comes from. I strongly suspect that the single threaded performance advantage is far narrower in legacy code that doesn’t take advantage of AVX.

    I’m glad the 2012 model was tested with a Radeon 7950. The ability to upgrade GPU’s matters and it’ll keep the 2012 model competitive for awhile. The system will support future video cards that come in from the PC side of things. With UEFI on video cards now, there is little difference between a Mac and PC version. For what it is worth, I have stuck an EVGA GTX 770 into a 2012 Mac Pro without issue and no modification on the video card or OS X drivers. It just works.

    A bit of a random note is that the GPU connector used in the Mac Pro isn’t new to Apple: they used it for the G4 class daughter cards form 15 years back.

    The PLX chip doesn’t have to do any port switching as a single GPU can drive up to 6 surfaces. That would imply the six DP signals from one GPU are routed in pairs to each of the Falcon Ridge controllers for encapsulation.

    One shocking thing is that wall power draw exceeds that of the PSU’s DC rating. That is worrying as the system itself has only a 450W rated power supply. Due to the AC to DC conversion, there is an efficiency factor but the system has to be running close to its DC limit. Performing several file transfers over powered Thunderbolt devices could put the power draw beyond the rated DC limit. I wonder if Apple has implemented throttling based upon raw power consumption of the system as a whole in addition to temperature and power consumption of individual parts. Perhaps testing the system on a 240V AC circuit would alter things here as it is more efficient power delivery?

    One aspect not accounted for is memory expansion. The 2009/2010/2012 Mac Pro’s will work with registered ECC memory which brings their maximum capacity up to 128 GB. Memory bandwidth too is superior in the dual socket 2010/2012 models: six channels of 1333 Mhz memory does have more bandwidth than four channels at 1866 Mhz. Going multi-socket does carry some overhead but still a bit of a disappointment that the theoretical number didn’t improve.
  • Bill Thompson - Wednesday, January 1, 2014 - link

    My guess is the nVidia-based iMac is faster with After Effects and Premiere because of CUDA.

    Davinci Resolve has been updated for OpenCL, but I don't think Octane or Adobe apps have.

    BTW, FCP X 10.1 displays multiple 4K streams in real time without rendering. It's a serious app.

Log in

Don't have an account? Sign up now