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

hotloop

v1.2.0

Published

Improves the accuracy/stability of Benchmark.js suites by executing each test in a separate Node.js process.

Downloads

548

Readme

Hotloop

Improves the accuracy/stability of Benchmark suites by executing each test in a separate Node.js process.

Installation

npm i hotloop --save

Usage

Put each benchmark in a separate file, like this:

// FILE: math-random.js
const { benchmark } = require("hotloop");

benchmark("Math.random()", () => {
    return Math.random();
});
// FILE: xkcd-random.js
const { benchmark } = require("hotloop");

// Credit: https://xkcd.com/221/
benchmark("Xkcd.random()", () => {
    return 4;   // chosen by fair dice roll.
                // guaranteed to be random.
});

Then create an index.js to execute the suite like this:

// FILE: index.js
const { run } = require("hotloop");

run([
    { path: "./math-random.js" },
    { path: "./xkcd-random.js" },
]);

Run the benchmark with node:

node index.js

A separate Node.js process is spawned for each benchmark and the results collected and summarized in a table like this:

┌─────────┬─────────────────┬──────────────────┬───────────┬─────────┐
│ (index) │      name       │     ops/sec      │    rme    │ samples │
├─────────┼─────────────────┼──────────────────┼───────────┼─────────┤
│    0    │ 'Xkcd.random()' │ '529,785,828.06' │ '±20.00%' │   49    │
│    1    │ 'Math.random()' │  '9,746,454.15'  │ '±37.29%' │   30    │
└─────────┴─────────────────┴──────────────────┴───────────┴─────────┘

Async/Promise Example

Use the 'benchmarkPromise()' function to benchmark async functions using promises.

// An iteration of a promise benchmark completes when the Promise
// returned by the async function is resolved.
benchmarkPromise(`Promise`, async () => {
    await myPromise;
});

Async/Callback Example

Use 'benchmarkAsync()' to measure async functions using a callback to signal completion rather than a returned Promise.

// An iteration of the async benchmark complete when the provided
// 'deferred.resolve()' function is invoked.
benchmarkAsync(`Async`, (deferred) => {
    setTimeout(() => {
        deferred.resolve();     // Complete the iteration
    }, 200);
});

Passing test arguments

Often it is useful to run multiple variations of the same benchmark (for example with different load parameters).

Use the 'args' parameter to pass configuration to your benchmark:

// Use 'args' to pass any JSON serializable object to the benchmark.
run([
    { path: "./random.ts", args: { generator: "Math" }},
    { path: "./random.ts", args: { generator: "Xkcd" }},
]);

Inside your benchmark, retrieve your test args using 'getTestArgs()'.

// Use 'getTestArgs()' to retrieve the args inside the benchmark file.
const args = getTestArgs();

// Use the test 'args' to choose which PRNG to benchmark:
const rng = args.generator === "Math"
    ? Math.random
    : () => 4;

benchmark(`${args.generator}()`, () => {
    return rng();
});

Debugging

See this project's .vscode/launch.json for examples of debugging benchmarks with VS Code.

Of particular note is the "--runInBand" option which executes all benchmarks inside the host process instead of spawning separate processes for each:

node index.js --runInBand