3 ms·
The article talks about three technologies, and IMHO none is about putting processes to background. The first one is about compressing pages instead of swapping
by eddieplan9 13y ago
The article talks about three technologies, and IMHO none is about putting processes to background. The first one is about compressing pages instead of swapping them to secondary storage. This should be a net gain in almost all scenarios. The second - App Nap - only applies to GUI applications, and there are opt-out controls. The third - Timer Coalescing - is the only one that has the potential to alter application behavior, and it only kicks in when the machines runs on battery.
- masklinn 13y agoApple seems to expect App Nap might create issues, the developer docs for the feature have a note indicating: > Note: If you experience problems with App Nap, you can temporarily disable it for a particular process by typing: > defaults write <app domain name> NSAppSleepDisabled -bool YES > Immediately file a bug describing the app and explaining how to reproduce the problem.
- jemeshsu 13y agoApple's note does not imply it's a design issue. Just that the software is not ready and bugs are expected.
- masklinn 13y ago> Apple's note does not imply it's a design issue. At no point did I imply that. I was replying to eddieplan9's declaration that > Timer Coalescing - is the only one that has the potential to alter application behavior by noting Apple thinks App Nap may do so.
- kunai 13y agoYou can also disable the whole thing by typing in defaults write NSGlobalDomain NSAppSleepDisabled -bool YES
- jasonjei 13y agoI'm really hoping there's a GUI way for the average user to disable it. Otherwise, writing to plist is not something easily done by the average user. Some apps aren't readily updated. Another thing Apple might do is publish a list of App Names and version/build number metadata to automatically disable it for apps known to have problems with AppNap.