Go to file
Dan Ballard 0b9266ba83 make writes to shared global hashmap threadsafe 2018-11-21 13:42:58 -08:00
.gitignore Initial commit 2017-04-06 16:35:15 +08:00
LICENSE Initial commit 2017-04-06 16:35:15 +08:00
README.md feat(dev): add error and update readme 2017-04-10 17:48:47 +08:00
pidusage.go make writes to shared global hashmap threadsafe 2018-11-21 13:42:58 -08:00
pidusage_test.go docs(dev): update readme.md 2017-04-07 23:10:33 +08:00

README.md

pidusage

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

Ideas from https://github.com/soyuka/pidusage but just use Golang

Go Report Card GoDoc

API

import (
  "os"
	"github.com/struCoder/pidusage"
)

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.

Linux

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.

On AIX

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.

Windows

Next version will support