GitXplorerGitXplorer
a

node-usage

public
389 stars
93 forks
28 issues

Commits

List of commits on branch master.
Unverified
6e0f896c9bcbfed3cb6a0784ad4f5c244ae85d0c

Update README.md

aarunoda committed 9 years ago
Unverified
6dcb60da3036812258f53400e0fc1a38ae25f82d

0.7.1

aarunoda committed 9 years ago
Unverified
00df59d517427ac4b28365a7b577349326f311fb

Update travis

aarunoda committed 9 years ago
Unverified
f5071a82cd9adc28bfd63559acb609991042ff5e

Merge pull request #51 from pvomhoff/master

aarunoda committed 9 years ago
Unverified
0162e3b9921d77de1cf29fbc397a2cfe26135394

nan lib need at least node 0.10 --> set required node version to 0.10.x

committed 9 years ago
Unverified
5f772c353bb030d68f2f91e09d01692b5a496a28

Update NAN module to version 2.0.9 and fix the c++ bindings.

committed 9 years ago

README

The README file for this repository.

Depricate Notice:

This project works. But there's a much better project with a similar API.
It even does not need a binary addon (So, it's easy to use).
See pidusage: https://github.com/soyuka/pidusage

node-usage Build Status

process usage lookup with nodejs

  • Simple interface to lookup cpu and memory usage of any accessible process on the system.
  • Works on OSX, Linux, SmartOS and Solaris
  • Tested on Heroku, Nodejitsu and Modulus

Example

Code

var usage = require('usage');

var pid = process.pid // you can use any valid PID instead
usage.lookup(pid, function(err, result) {

});

Result Object

{
	memory: 100065280, // in no of bytes
	memoryInfo: {
		rss: 15966208, // resident size memory in bytes
		vsize: 3127906304 // virtual memory size in bytes
	},
	cpu: 10.6 // in percentage
}

Average CPU usage vs Current CPU usage

This is only applicable for Linux

By default CPU Percentage provided is an average from the starting time of the process. It does not correctly reflect the current CPU usage. (this is also a problem with linux ps utility)

But If you call usage.lookup() continuously for a given pid, you can turn on keepHistory flag and you'll get the CPU usage since last time you track the usage. This reflects the current CPU usage.

see following example to enable keepHistory flag

var pid = process.pid;
var options = { keepHistory: true }
usage.lookup(pid, options, function(err, result) {

});

you can clear history cache too

usage.clearHistory(pid); //clear history for the given pid
usage.clearHistory(); //clean history for all pids