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 🙏

© 2025 – Pkg Stats / Ryan Hefner

node-distributed-multiprocessing

v0.0.1

Published

Easy distributed multiprocessing in nodejs

Readme

Easy Node Distributed Multiprocessing

About

node-distributed-multiprocessing aims at making distributed multiprocessing easy for anyone. Because NodeJS is single threaded, tasks that take up cpu can block any other progress of the program. This could cause your server to not accept any new requests. Multiprocessing in NodeJS solves this issue by handing off tasks to another process to complete, freeing up the main thread to handle io tasks.

This library has two parts; server and client. Server runs on each node that you want to have work on any tasks. Whereas client is a library that is used to connect to the nodes and dispatch tasks.

This library might be overkill for most projects. However, if you still need multiprocessing check out node-multiprocess for easy node multiprocessing on the local machine.

Getting started

Both the server and client can be installed using yarn and npm

$ npm i node-distributed-multiprocessing
$ # or
$ yarn add node-distributed-multiprocessing

Using the Server

The server can be set up on any server or node. After installing all you have to do to start up the server is import the package.

import node-distributed-multiprocessing/server
// server runs on port 50015 by default

The port can be changed by setting the SERVER_PORT environment variable. The server also loads any .env files so SERVER_PORT can also be set there as well.

Using the client

The client is what dispatches jobs to the nodes. The client can be import from the client module.

import DistributedPool from node-distributed-multiprocessing/client
// or
import { DistributedPool } from node-distributed-multiprocessing/client

To create the DistributedPool you have to pass in an array of URIs to your nodes where the server is running.

const pool = new DistributedPool(['localhost:50051', 'localhost:11223']);
// or
const pool = new DistributedPool([
    {
        host: 'localhost',
        port: '50051',
    },
    {
        host: 'localhost',
        port: '11223',
    },
]);

After the server has been created, the addJob method dispatches the supplied function to one of the nodes.

function fib(n: number): number {
    if (n <= 1) return 1

    return fib(n - 1) + fib(n - 2)
}

const result = await pool.addJob(fib, 10);
// result => 55