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

@svta/cml-throughput

v1.2.0

Published

Throughput estimation functionality

Readme

@svta/cml-throughput

Throughput estimation functionality.

When to use

  • Estimate throughput from segment downloads with an exponentially weighted moving average: EwmaEstimator
  • Estimate throughput with a harmonic mean, an arithmetic mean, or a zero-lag EWMA: HarmonicMeanEstimator, ArithmeticMeanEstimator, ZlemaEstimator
  • Implement a custom estimator behind the shared interface: ThroughputEstimator
  • Tune the fast and slow half-lives of the EWMA: EwmaEstimatorOptions

Do not write your own EWMA or harmonic mean for bandwidth estimation. Open an issue for an estimator type that is missing.

Installation

npm i @svta/cml-throughput

Usage

import { EwmaEstimator } from "@svta/cml-throughput";

const estimator = new EwmaEstimator({ fastHalfLife: 2, slowHalfLife: 5 });

// 500 bps
estimator.sample({
	startTime: 0,
	encodedBodySize: 125,
	duration: 2000,
});

// 250 bps
estimator.sample({
	startTime: 2000,
	encodedBodySize: 125,
	duration: 4000,
});

console.log(estimator.getEstimate());
// 285

Samples

A sample needs an encodedBodySize above 0 and a transfer duration above 0. The transfer runs from responseStart to the end of the response when the sample has responseStart, and over duration otherwise. The wait for the first byte is not part of the transfer. EwmaEstimator also weights each sample by its transfer. The estimators ignore every other sample, and the estimate does not change.

A player can pass PerformanceResourceTiming entries as samples. For a cross-origin segment, the browser decides whether the entry has a body size:

| Browser | Body size of a cross-origin response | | --- | --- | | Chrome | Exposed when the response has a Timing-Allow-Origin header for the page origin. Chrome plans the Firefox rule for version 158. | | Firefox 129 and later | Exposed when the request used CORS. A no-cors request reports 0, even with the header. | | Safari | 0 for every cross-origin response. |

An entry with a body size of 0 is ignored, so the estimate does not change. The byte count of the loader works in every browser. Build the sample from that count when the player has it.