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

throttled-reader

v1.0.1

Published

Node.js Readable stream capping average data rate by limiting reads from the source

Downloads

78,225

Readme

throttled-reader

npm version npm license travis build

This module is for throttling the data rate on a streams2+ Readable stream. This is not done by buffering but rather by rate-limited reading in paused mode, meaning the throttle is relatively close to the source.

Example use case: unlike other throttle modules that use buffering, this can be used to effectively throttle an incoming TCP stream, affecting the other side of the connection as well because the internal Node and OS buffers will congest.

Accuracy can be anywhere from <1% to over 25% depending on the rate and the kind of source. High rate limits, slower streams and streams with few/small buffers tend to be throttled more accurately. The utilities in test-util can be used to perform measurements with socket and file streams.

Basic usage

Just wrap your readable stream in a ThrottledReader instance, which is also a Readable. You can then use the throttled stream in its place. ThrottledReader must be the only consumer of the source stream's data!

var ThrottledReader = require('throttled-reader');

var throttledStream = new ThrottledReader(sourceStream, {
    rate: 10 * 1024 // In bytes per second
});

throttledStream.pipe(destinationStream);

Reference

Constructor: ThrottledReader(readableStream[, throttleOptions[, streamOptions]])

  • readableStream is the Readable to read from.

  • throttleOptions may contain the following options:

    Option | Default | Description ------------------ | ------- | ----------- rate | 0 | Average rate to throttle to (bytes/sec).   |   | Zero means unlimited. cooldownInterval | 100 | How often to determine whether reading may   |   | continue (ms). Lower values are more accurate   |   | but also introduce more processing overhead.

  • streamOptions may contain constructor options for the new Readable.

The data rate can be dynamically changed using getRate() and setRate(rate).