How to detect when the system is under pressure and you should reduce your work

Swift version: 5.6

Paul Hudson @twostraws May 28th 2019

You can – and should – read the thermal state of your device before doing any intensive work, because if the system is already under pressure you might find your app becomes unresponsive, even with basic things like animations.

You can read the current thermal state using ProcessInfo.processInfo.thermalState, which has four values:

When it’s .nominal you can proceed as normal and do all the work you want.
When it’s .fair you should consider delaying any work that isn’t visible to users.
When it’s .serious the system is working at high capacity and you should scale back the CPU, GPU, and I/O work you do.
When it’s .critical the system is unable to keep up with all the work that is being done, so your user interface is likely to stutter – now is a bad time to do any sort of animation.

The latter two of those are important to monitor, because users will notice – at .critical level you can expect their device to be hot to the touch, so hopefully your app isn’t the cause of that!