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

unix-mem-monitor

v1.0.4

Published

Provides tools to monitor memory usage on UNIX systems without ps for Lambda

Downloads

305

Readme

unix-mem-monitor

NPM package to monitor memory usage on Unix systems without ps, specifically made for AWS Lambda

For an example of using this on Lambda see the following SAM project: https://github.com/K-JBoon/lambda-mem-monitor

Usage

const MemMonitor = require('unix-mem-monitor');

...

// Instantiate a new MemMonitor and configure
const memMonitor = new MemMonitor({
    PID: process.pid, // Static PID to monitor, at least one of PID or PIDs must be specified
    PIDs: [ 1, 2, 3, 4, 5, 6 ], // Static PIDs to monitor, at least one of PID or PIDs must be specified
    monitorChildProcesses: true, // Optional configuration which makes MemMonitor automatically add all child processes of process.pid to the PIDs to monitor
    pollrate: 500 // Optional configuration to adjust the pollrate of MemMonitor, defaults to 1000ms
});

// Let MemMonitor initialize, during initialization the system's pagesize is acquired and monitoring jobs are started
await memMonitor.init();

/* MemMonitor emits a data event which contains statm data for all PIDs that are to be monitored
Structured as:

{
    PID1: {
            size:       [size in MB], // total program size
            resident:   [size in MB], // resident set size
            share:      [size in MB], // number of resident shared pages
            text:       [size in MB], // text (code)
            lib:        [size in MB], // library (unused since Linux 2.6; always 0)
            data:       [size in MB], // data + stack
            dt:         [size in MB]  // dirty pages (unused since Linux 2.6; always 0)
    },
    PID2: {
            size:       [size in MB], // total program size
            resident:   [size in MB], // resident set size
            share:      [size in MB], // number of resident shared pages
            text:       [size in MB], // text (code)
            lib:        [size in MB], // library (unused since Linux 2.6; always 0)
            data:       [size in MB], // data + stack
            dt:         [size in MB]  // dirty pages (unused since Linux 2.6; always 0)
    },
    ...
}
*/
memMonitor.on('data', data => {
    console.log(data);
});

// You can forcibly start the pull of new memory data with
memMonitor.updateMemoryData(); // Note: async!

// You can forcible start the updating of child processes with
memMonitor.updateChildProcesses(); // Note: async

// You can get current memory data at any time with
const currentMemoryData = memMonitor.memoryData;

/* You can get a reduced version (combined numbers of all processes) with MemMonitor.getMergedMemoryData()
Structured as:

{
    size:       [size in MB], // total program size
    resident:   [size in MB], // resident set size
    share:      [size in MB], // number of resident shared pages
    text:       [size in MB], // text (code)
    lib:        [size in MB], // library (unused since Linux 2.6; always 0)
    data:       [size in MB], // data + stack
    dt:         [size in MB]  // dirty pages (unused since Linux 2.6; always 0)
}
*/
const reducedMemoryData = memMonitor.getMergedMemoryData();

// You can unsubscribe all listeners and stop the polling process with
memMonitor.kill();