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

ssb-proc

v1.1.1

Published

expose process stats to sbot

Downloads

4

Readme

ssb-proc

add process stats to sbot status

example


> sbot plugins.install ssb-proc
> # now, restart sbot...

> sbot status

output: (snipped at ...)

{
  ...
  "proc": {
    "pid": 16873,
    "uptime": 170.073,
    "memoryUsage": {
      "rss": 187174912,
      "heapTotal": 75300864,
      "heapUsed": 68445192,
      "external": 21983959
    },
    "cpuUsage": {
      "user": 4679999,
      "system": 496666
    },
    "blockyness": 0.96,
    "loadavg": [
      0.37158203125,
      0.5224609375,
      0.45458984375
    ],
    "io": {
      "rchar": 78338626,
      "wchar": 796716,
      "syscr": 7711,
      "syscw": 1999,
      "read_bytes": 0,
      "write_bytes": 901120,
      "cancelled_write_bytes": 0
    },
    "net": {
      "lo:": {
        "rx": 740057,
        "tx": 740057
      },
      "wlp2s0:": {
        "rx": 214996,
        "tx": 111649
      }
    }
  }
}

status.proc

under the proc heading, are the following measurements

pid

the process identifier of the node process.

uptime

length of time in seconds that the current sbot process has been running.

memoryUsage

node.js process memory usage

blockyness

A the ratio of setIntervals that have fired in the last second. If this is not near 1 something must be hogging the CPU, possibly heavy loops.

loadavg

average cpu usage in the last minute, 5 minutes and 15 minutes.

io

output of /proc/{pid}/io

rchar and wchar is reads and write calls to the os, including cached reads. read_bytes and write_bytes is the actual bytes that have been read or written to disk, by this process since it started.

net

Bytes received (rx) and transmitted per network interface, taken from /proc/net/dev

Unlike the other measurements, This applies to the system as a whole and not the specific process. I would like to make it per process - any suggestions or PR most appreciated!

License

MIT