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

bench-cli

v0.1.0

Published

An easy-to-use CLI for running benchmarks

Downloads

16

Readme

Bench-CLI

Build Status npm version

Bench-CLI is an easy-to-use CLI for running benchmarks.

Installation

npm install -g bench-cli

Running Benchmarks

Running benchmarks is designed to be super simple and easy. You simply specify a path to the directory where your benchmark scenarios are located and then the number of iterations to run for each scenario.

bench <directory> --iterations <number>

If you don't specify a directory, the command will default to bench, relative to your current working directory.

Defining Benchmarks

Benchmarks are defined by creating a simple object export, known as a Bench. Each Bench defines a scenario function which represents the code to be benchmarked. They can optionally define several hooks which allow for setup and cleanup before and after runs.

module.exports = {
  // [Optional] Runs once before all of the scenario iterations
  setup() {},

  // [Optional] Runs once before each of the scenario iterations
  beforeScenario() {},

  // The benchmark scenario for which time is recorded
  scenario() {},

  // [Optional] Runs once after each of the scenario iterations
  afterScenario() {},

  // [Optional] Runs once after all of the scenario iterations
  cleanup() {}
};

Each of the above hooks, including scenario, is invoked with a context object that is empty by default. This allows information to be shared between the hooks, without having to rely on module state.

You can only define one scenario per Bench and, thus, per file. This limitation is in place to encourage isolation of benchmarking scenarios to help guarantee that you are getting accurate results.