I have seen few threads where it is clear some people think the M processor throttles right back after a short spell at load to control the temperature, so is not suitable for any sustained task.
To debunk this I have run my 2016 M5 at very high CPU load using HIARCS Deep Chess in analysis mode. This uses 350% CPU in Activity Monitor. I monitor CPU cycle GHz and CPU temp with Intel Power Gadget.
After starting HIARCS the CPU goes very quickly to the max multi-core overboost spec value of 2.4 Ghz. The temperature takes about 6 mins to reach about 92C. There after the CPU is throttled down to 2.3/2.4 to keep the temperature around 90C. After 30 minutes it settles down to 2.2 Ghz and 87C. It will stay at these levels indefinitely.
My 15" quad core runs at similar temperature doing the same thing. The casing is warm not hot.
The attached screenshot was taken 33 minutes after starting HIARCS running at 350% CPU.
If you want to try this yourself there are processes you can launch in Terminal to load the CPU instead of HIARCS.
EDIT ......added a screenshot after 58 mins
To debunk this I have run my 2016 M5 at very high CPU load using HIARCS Deep Chess in analysis mode. This uses 350% CPU in Activity Monitor. I monitor CPU cycle GHz and CPU temp with Intel Power Gadget.
After starting HIARCS the CPU goes very quickly to the max multi-core overboost spec value of 2.4 Ghz. The temperature takes about 6 mins to reach about 92C. There after the CPU is throttled down to 2.3/2.4 to keep the temperature around 90C. After 30 minutes it settles down to 2.2 Ghz and 87C. It will stay at these levels indefinitely.
My 15" quad core runs at similar temperature doing the same thing. The casing is warm not hot.
The attached screenshot was taken 33 minutes after starting HIARCS running at 350% CPU.
If you want to try this yourself there are processes you can launch in Terminal to load the CPU instead of HIARCS.
EDIT ......added a screenshot after 58 mins
Attachments
Last edited: