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

async-concurrency-pool

v0.1.5

Published

Simple pool for limiting concurrent asynchronous tasks

Downloads

39

Readme

Async-Concurrency-Pool

Node.js pool for limiting the number of asynchronous tasks that run concurrently.


Build Status Quality Gate Status Coverage npm Greenkeeper badge


Install

npm install async-concurrency-pool

Why?

Because I needed a simple mechanism to run an arbitrary number of tasks concurrently and didn't want to install a library with a bunch of features I don't need. It's written in typescript and the NPM package installs with the declaration files. It is intended to be used in node.js and uses native promises.

Usage

I mostly use this as a base class and as a result it is intentionally bare bones. A factory function createAsyncPool, the class itself AsyncPool and a helper class I use for testing LoopStats is exposed. ragent-pool is an example of a module that extends AsyncPool and includes implementation specific logic for how/when to return the agent to the pool.

import { createAsyncPool } from 'async-concurrency-pool';


class FooAgent {
  doSomethingAsync(n) {
        return new Promise((res)=>{
          setTimeout(()=>{
            res(n);
          }, 200);
        });
      }     
}
// this will be called with no arguments
// when a new instance of your agent is needed 
function agentFactory(){
  return new FooAgent();
}


async function doSomethingWithAgentPool() {
  const maxAgents = 2;
  const agentPool = createAsyncPool(agentFactory, maxAgents);
  
  let cnt = 0;
  
  
  /**
  *  The following loop will execute .doSomethingAsync 
  *  in parallel UNTIL `maxAgents` has been reached. 
  *  At that point all future calls to .doSomethingAsync will
  *  essentially execute in series moving to the 
  *  next iteration when the fastest pending async
  *  task in the pool completes
  **/
  
  for await(const agent of agentPool){
    
    // it is necessary to implement your own logic for 
    // breaking from the loop as the pool will loop indefinitely
    cnt += 1;
    if (cnt > 10){
      break;
    }
    
    // when the agent has completed the task you must manually call either
    // agentPool.add(agent) OR agentPool.remove(agent)
    // failure to do so will result in the loop pausing 
    // indefinitely once maxAgents has been reached as the 
    // pool is intentionally ignorant about when your 
    // agent has completed it's  work.
    agent.doSomethingAsync(cnt)
    .then((n)=>{
      // return the agent to the pool to be reused later
      agentPool.add(agent);
      return n;
    })
    .catch((err)=>{
      // remove the agent from the pool so it will not be used 
      agentPool.remove(agent);
      return err;
    })

    // NOTE: using .then .catch .finally on the agent 
    // allows tasks to be run in parallel 
    // using await agent.doSomethingAsync(cnt) would
    // result in everything being run in  series    
  }
}

Tests

npm run test