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

nodehog

v0.1.2

Published

A simple cpu hog utility.

Downloads

389

Readme

NodeHog

A simple resource hog utility.

Installation

Local use

npm i -g nodehog

Project use

npm i nodehog

Usage

This program can be used to create scheduled stress tests on a given target. Use cases include testing program performance under max CPU or Memory load, testing recovery from max load, and testing virtual autoscaling features such as the Kubernetes horizontal pod autoscaler.

Parameters

  • Type: The type of resource to stress (memory | cpu)
  • Lifespan: The length of the stress period in milliseconds
  • Deathspan: The length of the relief period in milliseconds
  • Iterations: The number of cycles to complete before NodeHog exits (1 cycle = 1 lifespan + 1 deathspan)

CLI

$ nodehog cpu 30000 30000 3

╔═════════════════════════════════════════════════/
║  nodehog     cpu      30000     30000     3
╚═══════════════════════════════════════════════/
     |          |         |         |       |
     |          |         |         |       |
  command       |         |         |       |
               type       |         |       |
                     lifespan(ms)   |       |
                             deathspan(ms)  |
                                        iterations

Programmatically

const NodeHog = require('nodehog');

new NodeHog('memory', 30000, 15000, 10).start();

If you find this useful, leave a star! If it can be improved in any way for your use case, fork it, send a PR, or just let me know 😃