Here is the LaunchDaemon plist that I have been using to collect this information in the background on my test machines.Ĭom.Ĭom.’s note: We’ve updated this guide with a new pick for monitoring your Mac and keeping it performing as it should. This will give you relative performance statistics to help determine the qualitative “feel” and “slowness” an application may be causing.

Compare native processes like WindowServer, Safari, and Mail to the target application.

A simple example would be: “reboot, immediately run target application, perform X task in target application, stop log collection”

Create a repeatable testing plan so you can change variables and maintain data integrity.

Use some analysis tool like Splunk, Kibana, or event Excel instead of trying to read the logs manually.If the application you are testing uses a kernel extension be sure to chart kernel_task with that KEXT loaded and without that KEXT loaded.While we have since moved to more advanced ways to collect energy impact and performance telemetry for cmdReporter’s internal testing, I have run the above command as a LaunchDaemon on my own machine for months at a time without noticing any additional overhead.

Mac os cpu usage