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

howslow

v0.1.0

Published

Simple JS performance testing

Downloads

1,882

Readme

howslow

Easy performance testing in JavaScript!

npm i howslow
import howSlow from "howslow";

await howSlow("sum", (start, stop) => {
  start();
  let sum = 0;
  for (let i = 0; i < 1e7; i++) {
    sum += i;
  }
  stop();
});

To see how slow our code is, run the snippet above in node, deno or the browser. Timing statistics will be logged to the console:

sum

First run after start:
10.90 ms

Average of 50x after warm-up of 10x:
8.53 ± 0.12 ms

We have two different metrics which can both be important performance considerations: For example, "first run after start" can indicate how long something would take on page load. The warmed-up, averaged timing is relevant for code that runs often. The latter is usually much faster because it can benefit from compiler optimization.

Multiple timings

You can also have multiple related timings and give them labels:

import howSlow from "howslow";

await howSlow("json", (start, stop) => {
  let array = Array(1e6).fill(1);

  start("stringify");
  let json = JSON.stringify(array);
  stop();

  start("parse");
  array = JSON.parse(json);
  stop();
});

Which prints:

json

First run after start:
stringify:      35.13 ms
parse:          19.35 ms

Average of 50x after warm-up of 10x:
stringify:      25.30 ± 2.85 ms
parse:          14.20 ± 0.68 ms

Configuration

You can specify the number of timed runs and warm-up runs in an optional third argument:

howSlow("test", () => {}, {
  numberOfRuns: 200,
  numberOfWarmups: 20,
});

API

function howSlow(
  name: string,
  run: (
    start: (label?: string) => void,
    stop: (label?: string) => void
  ) => void,
  options?: {
    numberOfRuns: number;
    numberOfWarmups: number;
  }
): Promise<void>;