macOS ARM - Incorrect process CPU times

[andrewkroh]

Based on similar code in other projects it looks like the process CPU times may not be scaled correctly on Apple M1 / M2 hardware. This code needs to apply a scaling factor from https://developer.apple.com/documentation/driverkit/mach_timebase_info_t to the ticks. Under intel macs these were simple 1 tick = 1 nanosecond so it just worked.

go-sysinfo/providers/darwin/process_darwin.go

Lines 155 to 156 in f544eca

	User: time.Duration(task.Ptinfo.Total_user),
	System: time.Duration(task.Ptinfo.Total_system),

Related

• https://openradar.appspot.com/radar?id=5055988478509056
• cpu time off by a factor of 40x on M1 Macs gosigar#168
• macOS ARM - incorrect process CPU times elastic-agent-system-metrics#79

[nickelnickel]

@andrewkroh do you know if there is a plan to address this issue? As noted in elastic/gosigar#168 we have confirmed this is affecting measurements by our product which relies on this for CPU measurements.

[andrewkroh]

I'm not aware of any teams that have this on their plan at the moment. Contributions are welcomed.