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 🙏

© 2026 – Pkg Stats / Ryan Hefner

measure-loop

v0.1.0

Published

An accurate, runtime-agnostic benchmarking loop.

Readme

measure-loop

An accurate, runtime-agnostic measure loop for benchmarking purposes.

Usage

import { gc } from 'measure-loop/detect/gc'; // Auto detect available sync GC function
import { hrtime } from 'measure-loop/detect/hrtime'; // Auto detect available hrtime function

import { createSideEffect } from 'measure-loop/side-effect';
import { createLoop, warmupLoop } from 'measure-loop';

const loop = await createLoop(
  () => {
    createSideEffect(performance.now());
  },
  gc,
  hrtime
);
warmupLoop(loop);

// Run and collect timings
const runs: number[] = [];
loop(runs, [], []);
console.log('runs:', runs);

To run:

bun run bench.ts

# Expose manual GC for V8-based runtime.
node --expose-gc bench.ts
deno run --v8-flags=--expose-gc bench.ts
...

To collect GC time:

import { gc } from 'measure-loop/detect/gc';
import { hrtime } from 'measure-loop/detect/hrtime';
import { detectHeapUsage } from 'measure-loop/detect/heap-usage';

import { createSideEffect } from 'measure-loop/side-effect';
import { createLoop, warmupLoop } from 'measure-loop';

const loop = await createLoop(
  () => {
    createSideEffect(performance.now());
  },
  gc,
  hrtime,
  { measureGC: true }
);
warmupLoop(loop);

// Run and collect timings
const runs: number[] = [];
const gcs: number[] = [];

loop(runs, gcs, []);

console.log('runs:', runs);
console.log('gcs:', gcs);

To collect heap usage:

import { gc } from 'measure-loop/detect/gc';
import { hrtime } from 'measure-loop/detect/hrtime';
import { detectHeapUsage } from 'measure-loop/detect/heap-usage';

import { createSideEffect } from 'measure-loop/side-effect';
import { createLoop, warmupLoop } from 'measure-loop';

const loop = await createLoop(
  () => {
    createSideEffect(performance.now());
  },
  gc,
  hrtime,
  {
    heapUsage: await detectHeapUsage()
  }
);
warmupLoop(loop);

// Run and collect timings
const runs: number[] = [];
const heaps: number[] = [];

loop(runs, [], heaps);

console.log('runs:', runs);
console.log('heaps:', heaps);

Note that collecting heap usage can increase variation of other samples.

Other options

await createLoop(
  ...,
  {
    // Number of calls in an iteration
    batch: 4096,

    // Calls to inline
    inlineCalls: 4

    // With batch = 4097 and inlineCalls = 4:
    // for (let i=0;i<1024;i++){fn();fn();fn();fn()}fn();
  }
);

// Warmup the loop, stops when running time > threshold and total iterations > iters
warmupLoop(loop, threshold?, iters?);

The loop implementation is based on mitata. Check it out it's a good library :).