UPDATE: since updating to macOS 10.14 this issue is not occurring to me anymore.
I have a long running Python process (using multiprocessing), run from Terminal, and regularly come back to it realizing that it has been suspended for several hours while I was away from the Mac. The moment I get back to it it's running again at normal speed (it's displaying a progress bar in Terminal). This is despite:
- checking "prevent computer from going to sleep automatically when the display is off" in the Energy Saver preferences panel
caffeinatefrom the parent process (
Popen('caffeinate')), which does show up in the Energy section of Activity Monitor
- Using appnope to begin an activity with
NSActivityUserInitiated | NSActivityLatencyCritical
This happens on multiple Computers, but has only started happening recently, i.e. I don't think it occurred before 10.13.
Why could this be occurring, and what other means are there to investigate or prevent it?