npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

pm2-usage

v0.3.9

Published

simple way to lookup linux process usage

Downloads

5

Readme

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 and Nodejitsu

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

{ 
	cpu: 10.6, //in percentage
	memory: 100065280 //in no of bytes
}

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

Motivation

  • Some of the NodeJS PAAS providers do not expose an interface to monitor CPU and Memory usage.
  • They asks us to go for somewhere else for that which I don't want to go (or simply I cannot go)
  • So node-usage was born to tackle on this.