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

node-red-contrib-lyteworx-cluster

v0.1.0-alpha.11

Published

A multi-processing cluster node for Node-RED

Downloads

14

Readme

node-red-contrib-lyteworx-cluster

Run Node-RED on all your CPU cores

Description

The Node-RED framework runs on Node.js®, which by default runs in a single process and which uses a single cpu core. This node allows Node-RED to run flows on multiple cores.

Most computers, from the smartphone to the enterprise server, have multiple cores. To take advantage of this, Node.js has a module (called the cluster module) that allows a Node.js program to run on multiple cores.

License

This node is licensed under the Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License.

For commercial use, please contact [email protected]

Getting Started

Installing

npm i node-red-contrib-lyteworx-cluster

Overview

The cluster node auto-detects the runtime environment of the Node-RED instance in which it is running. Once a single cluster node is added to a flow, on the next deploy the node will call the Node.js cluster module. The process that was originally running the Node-RED instance becomes the master process, which spawns multiple worker processes.

If all nodes are removed from the active flow, all clustering logic will also be removed, and Node-RED will function as normal.

Terminology

  • Cluster: A set of processes running on a single computer instance that can talk to each other using Inter-Process Communication (IPC)

  • Worker: A single process in a cluster.

  • Master: A single process that acts as the parent to all Worker processes. A Master process can create and stop worker processes.

  • Bingo Worker: A single worker process out of all of the worker processes spawned that can be used for single-process tasks. For example, if Node-RED is watching a file, the user may only want to execute a flow once per event, and not have every worker process fire at once.

  • Broadcast: Send a message to every worker in the cluster at the same time.

  • Round Robin: Cycle through workers one at a time, sending a message to the next worker in order.

Runtime Modes

  1. Enable Clustering - The default mode, which enables clustering (running all flows on all processes)

  2. Send to Random Worker - Takes a message from the input and sends it to a random worker process.

  3. Run On Bingo Process - Only passes the message to the output if the current worker is the bingo worker. Does not allow the message to continue to if the worker is not the bingo worker.

  4. Send To Bingo Process - Takes a message from the input and sends it to the bingo worker.

  5. Broadcast - Takes the message and sends it to all available workers.

  6. RoundRobin - Passes the message to the next worker selected using a round-robin scheduling algorithm.