You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
strucoder 5e29cda97c v0.1.2 5 years ago
.gitignore Initial commit 5 years ago
LICENSE Initial commit 5 years ago feat(dev): add error and update readme 5 years ago
pidusage.go v0.1.2 5 years ago
pidusage_test.go docs(dev): update 5 years ago


Cross-platform process cpu % and memory usage of a PID for golang

Ideas from but just use Golang

Go Report Card GoDoc


import (

func printStat() {
	sysInfo, err := pidusage.GetStat(os.Process.Pid)

How it works

A check on the runtime.GOOS is done to determine the method to use.


We use /proc/{pid}/stat in addition to the the PAGE_SIZE and the CLK_TCK direclty from getconf() command. Uptime comes from proc/uptime

Cpu usage is computed by following those instructions. It keeps an history of the current processor time for the given pid so that the computed value gets more and more accurate. Don't forget to do unmonitor(pid) so that history gets cleared. Cpu usage does not check the child process tree!

Memory result is representing the RSS (resident set size) only by doing rss*pagesize, where pagesize is the result of getconf PAGE_SIZE.

On darwin, freebsd, solaris

We use a fallback with the ps -o pcpu,rss -p PID command to get the same informations.

Memory usage will also display the RSS only, process cpu usage might differ from a distribution to another. Please check the correspoding man ps for more insights on the subject.


AIX is tricky because I have no AIX test environement, at the moment we use: ps -o pcpu,rssize -p PID but /proc results should be more accurate! If you're familiar with the AIX environment and know how to get the same results as we've got with Linux systems.


Next version will support