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

@timkendrick/benchmark-cli

v1.0.0

Published

Command-line performance benchmarking for JavaScript

Downloads

4

Readme

@timkendrick/benchmark-cli

npm version Stability

Command-line performance benchmarking for JavaScript

Simple command-line tool for running performance benchmark suites, providing direct speed comparison between related tests.

High-resolution results are generated by Benchmark.js.

Installation

Within a project:

npm install @timkendrick/benchmark-cli --save-dev

System-wide:

npm install -g @timkendrick/benchmark-cli

Usage

benchmark suite1.js [suite2.js] [...suite3.js]

…where the input files are CommonJS modules that export one of the following:

  • An anonymous test function
  • A key/value object with test names as keys and test functions as values
  • An array whose items are of one of the above

Named tests within the same key/value object will be run against each other for comparison of results.

Inline scripts can also be passed via the command line using the -e argument:

benchmark -e "() => { new Array(1000).fill('a'); }" -e "() => { for (let i = 0, arr = []; i < 1000; i++) { arr.push('a') } }"

Inline scripts must conform to the same rules as the permitted CommonJS module export formats.

Example output

Running benchmarks.js #1 (1 of 3):
✔ Native map/filter/slice (100 items) x 13,357 ops/sec ±1.67% (82 runs sampled)
✔ Transducer map/filter/slice (100 items) x 19,000 ops/sec ±1.70% (81 runs sampled)
Transducer map/filter/slice (100 items) is 42.24% faster

Running benchmarks.js #2 (2 of 3):
✔ Native map/filter/slice (1000 items) x 1,355 ops/sec ±1.36% (84 runs sampled)
✔ Transducer map/filter/slice (1000 items) x 5,468 ops/sec ±1.93% (82 runs sampled)
Transducer map/filter/slice (1000 items) is 303.58% faster

Running benchmarks.js #3 (3 of 3):
✔ Native map/filter/slice (10000 items) x 132 ops/sec ±1.71% (70 runs sampled)
✔ Transducer map/filter/slice (10000 items) x 7,694 ops/sec ±1.71% (82 runs sampled)
Transducer map/filter/slice (10000 items) is 5723.27% faster