You can use Signposts readily from scripting languages, shell scripts, even within 3rd party apps, with the aid of these tools.
performance
With a shiny new high-speed Samsung X5 SSD to test, I was looking forward to some real speed. Did it deliver good value for its high price, though?
What should you do with a Mac whose fans keeping coming on full blast, with high CPU loads from kernel_task, and sluggish performance?
It’s hot, you’re hot, and your Mac has slowed right down. Activity Monitor tells you that it’s kernel_task which is to blame. Is macOS playing up, or what?
Both are now notarized for added security, there is a small bug fixed in Consolation, and updated documentation.
At last: RouteMap performs some analysis on your Signposts, and with the other tools can be used to estimate latency, and look at macOS system performance too.
Picking the right time system for the purpose is critical when you want to analyse very short periods. Sometimes it takes time to discover how to juggle with time.
Doesn’t writing so much to the unified log result in performance penalties? So how can Apple expect us to use the log and Signposts to measure performance?
Blowhole 7 now writes proper Signposts in Mojave, as well as Pseudo-Signposts in Sierra and High Sierra.
A new version of Blowhole, the second alpha of RouteMap, and a complete tutorial toolkit to help you get started using log Signposts from Sierra to Mojave.
