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

@feltmaps/benchmarking

v1.1.0

Published

A benchmarking tool for JS code

Downloads

1

Readme

Felt benchmarking

This package allows to benchmark javascript code on the browser.

How it works

Runs Benchmark implementations and measures the time it takes to execute a single run. If that run takes less than 5ms (which is the minimum resolution of performance.now(), see Performance.now() on MDN), we keep incrementing the number of iterations iterationsPerSample per run until it takes more than 5ms. Once that happens, we capture 210 samples via running iterationsPerSample iterations per sample

Create a benchmark

export default class FilterCreate extends Benchmark {
  bench() {
    findPrimes(1000);
  }
}

Create a benchmark suite

const suite = new BenchmarkingSuite();

Add benchmarks to the suite

suite.register("Filter", "version 1", new FilterCreate());

Adding multiple benchmarks with the same name but different version will compare them in the results website

suite.register("Filter", "version 1", new FilterCreate());
suite.register("Filter", "version 2", new FilterCreate2());

Run the suite

suite.run();

See index.html and benchmarks.ts for website and js code examples

Results

Results show a statistics table, a plot with various statistics (quartiles, median, mean, trimmed mean) and a regression plot.

The correlation in the table should be almost 1, if it's less than 0.99 a ⚠️ sign is shown. If correlation is less than 0.9 a ☠ sign is shown because results are not valid.

alt text

Based on Maplibre's benchmarking tool