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

sz-throttler

v1.0.0

Published

Throttler implementation to allow a maximum number of executions of some code block in a given time window across multiple instances

Downloads

5

Readme

SZ Throttler

Throttler implementation to allow a maximum number of executions of some code block in a given time window across multiple instances.

This library uses Redis, to synchronize the execution, so you must have the same instance running and accessible to all instances with throttled code.

When the maximum number executions is reached, any new executions will be queued in a pool, waiting for a chance to be executed. This is when the things here are unique, as instead of waiting for all time window to pass to execute the next block, this implementations always check how many executions happened since X seconds ago (x is the time window) and execute a new block if this number is less then the configured limit.

Usage

Install and import

Install the lib: npm install sz-throttler

Import in the application:

const SZThrottler = require( 'sz-throttler' );

Create a new throttler

const throttler = new SZThrottler( redisClient ).getThrottler( 'my_throttler', 10, 5, false );

Instantiate a new throttler using a valid Redis client instance.

Than call .getThrottler to create a new throttler function. It can receive 4 parameters:

  • name {String} Name of the throttler. Unique to the block of code intended to be executed, but will be the same across all the instances
  • maxConcurrency {Number} Number of execution in the time window
  • timeWindow {Number} The time window
  • waitForNotification {Boolean} If this is true, the executed blocks will still be accounted on subsequent time windows until the code explicit calls a callback function.

Usage

throttler(function () {
  // myCode...
});

or, with the fourth parameter true:

throttler(function ( notifyExecutionDone ) {
  // do shit ...
  notifyExecutionDone();
});

Need to stop ASAP

throttle._kill();