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

stats-beat

v1.0.1

Published

Node.js performance statistics emitter

Downloads

5

Readme

stats-beat

Node.js performance statistics emitter

Install

npm install --save stats-beat

Note: requires node v4 or higher.

Usage

const statsBeat = require('stats-beat')();

var app = express();
//...
var server = app.listen(PORT);
statsBeat.start({ server });
export STATS_BEAT=all
npm start

Then all performance metrics will be prtinted on the console each 5 seconds

{"sysload%":18,"freememMB":3661,"cpu%":112,"rssMB":152,"heapMB":64,"rps":3149,"resTime_ms":20.887753158529616,"reqBytes":116,"resBytes":114849,"rxKBs":365,"txKBs":361653,"numconn":80,"evloop_us":6646}

To report only CPU and memory ech 2s, use this command:

export STATS_BEAT='period=2&cpu&rss'
npm start

You can register a listener to process the performance metrics in a custom way, e.g. write them in a csv file or send them to a central service.

const statsBeat = require('stats-beat')();

var app = express();
//...
var server = app.listen(PORT);
statsBeat.start({ server });
statsBeat.on('stats', (stats) => {
  // process stats
});

Reference

Stats

| Selector | Property | Description | |------------|--------------|----------------------------------------| | sysload | sysload% | 1 minute system load average as %. See os.loadavg() | | freemem | frememMB | Free system memory in MB. See os.freemem() | | cpu | cpu% | Process CPU usage as % of one logical core. Requires node v6.1. See process.cpuUsage() | | rss | rssMB | Process memory (resident set size) in MB. See process.memoryUsage() | | heap | heapMB | V8 heap used. See process.memoryUsage() | | rps | rps | Completed requests per second. | | restime | resTime_ms | Response time in ms. | | reqbytes | reqBytes | Total request size in bytes. | | resbytes | resBytes | Total response size in bytes. | | rxrate | rxKBs | KB received per second | | txrate | txKBs | KB sent per second | | numconn | numconn | Number of concurrent connections on the server. See server.getConnections() | | evloop | evloop_us | Node event loop latency in microseconds |