You mean this:
App Nap, designed to preserve the energy used by inactive apps, cuts down on the power usage of an app that is not running in the foreground. When an app’s window is not visible (minimized to the dock, for example) it is considered to be “napping”, which causes OS X to put it into a low-power state regulating its CPU usage and throttling both timers and input/output activity. This reduces power, but it also prevents napping apps from interfering with the processes of active apps.
Developers are able to prevent their apps from using App Nap on a per app basis, but the feature should provide significant improvements in CPU idle time for apps that would otherwise attempt to frequently access data in the background.


On 25 October 2013 00:21, tim Rowledge <> wrote:

Looking through some of the low-level changes in Mavericks I noticed stuff about timer consolidation. I *think* that it is something that you can offer to allow, rather than something done unto you code, but almost certainly it will have some sort of impact on the heartbeat ticker type of code used in stackvm/cog. Where is a skilled Mac vm maintainer when you need one?

tim Rowledge;;
"bOtHeR" said Pooh, mistaking the LSD tablet for aspirin

Best regards,
Igor Stasenko.