It seems like there’s always some controversy surrounding new Apple hardware. These devices are some of the most popular in the world, which means that they’re bound to get closely scrutinized, perhaps more so than any other tech product on earth.
With that said, there’s a brewing controversy over CPU throttling in the new MacBook Pro. Of course, throttling on a laptop as thin as the MacBook Pro is to be expected, but issue has been taken with the amount of throttling present in Apple’s high-end 6-core Core i9-powered machine.
The scrutinization is warranted, especially when you consider that the least-expensive Core i9 MacBook Pro sells for $ 2,700. If you opt to max out the GPU, RAM, and SSD storage, the price quickly balloons to nearly $ 7000 after tax.
Just how bad is CPU throttling on the 2018 MacBook Pro? Let’s do a brief export test with Final Cut Pro X to investigate further.
I opted to use Final Cut Pro X in these tests for the simple reason that it is Apple’s flagship NLE, and many of the people purchasing these machines are creative professionals who work in video.
To monitor CPU performance, I used Intel’s excellent Power Gadget software, which is a free download for Mac users.
Here is my configuration for the test:
- A four minute, 4K video shot at 60 frames per second with a Panasonic GH5. (Not rendered and unoptimized).
- Exported with Apple’s built-in Final Cut Pro preset: Web Hosting – H.264 Faster Encode – 3840 x 2160.
- Same exact setup used with both tests.
- All other apps, except apps needed for testing, closed.
- Power plugged in, except for the [spoiler: freezer test.]
To preface, this test is by no means law, and certain applications and export settings may respond differently.
First test: Stock 6-core export
Leaving the Core-i9 configured as default, I exported the video in 5 minutes and 30 seconds. Throttling was definitely noticeable during the export, as you can see from the following chart created from Intel Power Gadget log data:
Specifically, notice how aggressive throttling is here, with numerous occurrences of the clock speed dipping to 800MHz. According to Intel Power Gadget data, this is in response to a CPU Hotflag.
Like most laptops, previous generations of the MacBook Pro have throttled, but the throttling with the Core i9 can be quite aggressive with Final Cut Pro X exports.
Second test: 4-core export
I was curious to see how the MacBook Pro would respond to the same test with only 4 cores enabled. To attempt this, I installed Xcode, and utilized the handy Instruments utility to disable two of the cores.
I now effectively had a quad-core machine instead of a hexa-core machine. Would it make any difference for my Final Cut Pro export?
Surprisingly, yes. The export completed in just 5 minutes and 12 seconds, 18 seconds faster than the it did when using all 6 cores. Notice the difference in throttling. Although still present, you’ll definitely spot fewer dips to 800 MHz when only 4 cores are utilized.
Using just four cores (eight logical cores with Hyper-Threading)
Keep in mind that the CPU inside this MacBook Pro has the following specifications:
- Base clock: 2.9 GHz
- Turbo Boost: 4.8 Ghz
- Cores: 6
- TDP: 45W
For the majority of the testing, the wattage consumed by the CPU stayed around 20W, and overall CPU utilization stayed well below 50%.
Third Test: The freezer
For the last test, I switched back to the full 6-cores and put my MacBook Pro in the freezer to keep it cool, à la Dave Lee, who made the excellent video that lended such a big voice to this issue. Unsurprisingly, doing so resulted in the best performance out of the three tests. The video exported in just 4 minutes and 51 seconds, 21 seconds faster than the quad-core test, and 39 seconds faster than the hexa-core test without the extra cooling.
Notice that there are no dips to 800 MHz when using your MacBook Pro in the freezer, although the CPU still hangs out well below the 2.9 GHz base clock speed. The freezer is good for short term performance on the MacBook Pro, but may prove to be an inconvenient/hazardous working environment (condensation is bad, folks).
iMac Pro Test
Lastly, I wanted to see how my iMac Pro compared, since it has plenty of thermal overhead along with an 8-core Xeon CPU. Would it easily best the MacBook Pro?
Just by looking at this graph, you would think so. The CPU basically stays locked at 4.0GHz and above, and as you can see its temperatures remain relatively cool. However, the iMac Pro actually proved to be slowest on export, coming in at 6 minutes flat, a full 30 seconds slower than our slowest export with the MacBook Pro.
Why? Xeon CPUs lack onboard hardware video encoding, dubbed Intel Quick Sync Video. So even though the iMac Pro runs circles around the MacBook Pro from a thermal perspective, it doesn’t really matter in this test. That’s why you can’t always look at pure numbers when judging a machine. Lots of variables go into measuring the performance, and it differs based on the applications you plan to use.
Unfortunately, I don’t have a Core i7 version of the 2018 MacBook Pro to compare with the i9 version. It’s possible that it may perform better than the i9 version when using all 6 cores in this test, but I’d have to try it to be sure.
The results of this test are by no means a recommendation to stay away from the high end MacBook Pro. A machine should be judged on all of its merits and further testing is required before I’m able to do so. That said, the optics aren’t particularly good for Apple; it’s reasonable for users to expect more cores to equal better performance, especially with an app that was built from the ground up with Mac hardware in mind.
All blame shouldn’t rest on Apple’s shoulders, though. Intel needs better performing chips from a thermal perspective. It’s one major reason why Apple’s rumored transition to ARM Macs could prove to be a great thing for future laptops coming out of Cupertino.
What do you think? Is this a serious issue, or is it making a mountain out of a molehill? Sound off in the comments with your thoughts.
Subscribe to 9to5Mac on YouTube for more Apple news:
Let’s block ads! (Why?)