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

benchee

v1.1.0

Published

Simple benchmarks in both node and browser

Downloads

130

Readme

benchee

Simple benchmarks in both node and browser

Table of contents

Requirements

benchee requires that Promise is available globally. If using an environment that does not support it, you should polyfill prior to importing benchee.

Usage

import { benchmark, createSuite } from "benchee";

// the functions to benchmark
const add = (a, b) => a + b;
const subtract = (a, b) => a - b;

// create an individual benchmark
benchmark("add", () => add(1, 2)).then(results => console.log(results));

/*
{
  "stats": {
    "elapsed": 677,
    "endTime": 1540050973491,
    "startTime": 1540050972814,
    "iterations": 82165907,
    "ops": 121367661,
    "tpe": 0.00000823942708987561
  },
  "name": "add"
}
*/

// or create a suite of benchmarks
createSuite()
  .add("add", () => add(1, 2))
  .add("subtract", () => subtract(1, 2))
  .run()
  .then(results => console.log(results));

/*
{
  "ungrouped": [
    {
      "stats": {
        "elapsed": 802,
        "endTime": 1540050973617,
        "startTime": 1540050972815,
        "iterations": 28777534,
        "ops": 35882211,
        "tpe": 0.000027868961947886152
      },
      "name": "add"
    },
    {
      "stats": {
        "elapsed": 750,
        "endTime": 1540050974473,
        "startTime": 1540050973723,
        "iterations": 106326932,
        "ops": 141769242,
        "tpe": 0.000007053716174186235
      },
      "name": "subtract"
    }
  ]
}
*/

The results contract is Promise-based, however you can also access the results in a callback format if preferred.

Benchmark groups

In addition to running standard benchmarks, you can group benchmarks together within the same suite. The results of each group can be accessed through the onGroupComplete callback, and will namespaced under the group name in the final results.

To apply a group, simply add a group name as the second parameter to your test.

createSuite()
  .add("add", "math", () => add(1, 2))
  .add("trim", "string", () => "  trimmed  ".trim())
  .run()
  .then(results => console.log(results));

/*
{
  "math": [
    {
      "stats": {
        "elapsed": 888,
        "endTime": 1540051045206,
        "startTime": 1540051044318,
        "iterations": 38415463,
        "ops": 43260656,
        "tpe": 0.000023115691720284616
      },
      "name": "add"
    }
  ],
  "string": [
    {
      "stats": {
        "elapsed": 568,
        "endTime": 1540051045880,
        "startTime": 1540051045312,
        "iterations": 15363261,
        "ops": 27047994,
        "tpe": 0.00003697131748266205
      },
      "name": "trim"
    }
  ]
}
*/

Statistics

Statistics for each benchmark have the following shape:

{
  // time of total benchmark run
  elapsed: number;
  // timestamp of benchmark complete
  endTime: number;
  // number of operations executed in benchmark
  iterations: number;
  // operations per second calculation
  ops: number;
  // time per execution calculation
  tpe: number;
  // timestamp of benchmark start
  startTime: number;
}

Options

delay

The time wait between execution of benchmark groups (defaults to 100ms)

minIterations

The minimum number of iterations that need to occur before the benchmark is considered complete (defaults to 10)

minTime

The minimum amount of time that needs to elapse before the benchmark is considered complete (defaults to 500ms)

NOTE: This is ignored when type is set to fixed.

onComplete

Function called when suite has finished running. This is the callback method to receive results, if preferred over the standard promised-based method.

onComplete: (results: Benchee.Results) => void;

onGroupComplete

Function called when a given group has completed all of its benchmarks.

onGroupComplete: (results: Benchee.ResultsGroup) => void;

onGroupStart

Function called when a given group has started running its benchmarks.

onGroupStart: (group: string) => void;

onResult

Function called when a specific benchmark has finished running.

onResult: (result: Benchee.Result) => void;

type

The type of benchmark to perform. (defaults to adaptive)

Valid values:

  • adaptive => number of iterations performed is based on an exponential algorithm driven by the minTime
  • fixed => number of iterations performed is based directly on minIterations

Support

Browser

  • Chrome (33+)
  • Edge (all)
  • Firefox (29+)
  • Opera (20+)
  • Safari (7.1+)

NOTE: If a Promise polyfill is provided, then older versions / unlisted browsers should be supported as well (notably IE11).

Node

  • 6+

Development

Standard stuff, clone the repo and npm install dependencies. The npm scripts available:

  • build => run rollup to build the distributed files in dist
  • clean => run rimraf on the dist folder
  • dev => run webpack dev server to run example app (playground!)
  • dist => runs clean, build, and build:types
  • lint => runs TSLint against all files in the src folder
  • lint:fix => runs lint, fixing any errors if possible
  • prepublish => runs prepublish:compile
  • prepublish:compile => run lint, test:coverage, and dist
  • test => run Jest, testing functions with NODE_ENV=test
  • test:coverage => run test but with code coverage output
  • test:watch => run test, but with persistent watcher