Fast implementation of memory pool in JavaScript.
Shared memory pool — collective knowledge across swarm agents
JavaScript Memory Pool implementation
A fast, efficient Node.js Worker Thread Pool implementation
Connection pool for node-postgres
A general purpose buffer pool.
OpenTelemetry instrumentation for `generic-pool` resource pool for managing expensive resources
TypeScript definitions for pg-pool
A minimal and tiny Node.js Worker Thread Pool implementation, a fork of piscina, but with fewer features
Generic resource pooling for Node.JS
Resource pooling for Node.JS
Postgres query result returned as readable stream
requestAnimationFrame pool to avoid busyness on the thread
Workers Vitest integration for writing Vitest unit and integration tests that run inside the Workers runtime
Map-like, concurrent promise processing for Node.js
Simple and robust resource pool for node.js
Offload tasks to a pool of workers on node.js and in the browser
Reuse typed arrays
Lightweight worker pool using NodeJS worker_threads
Runs Promises in a pool that limits their concurrency.
A node.js driver for mysql. It is written in JavaScript, does not require compiling, and is 100% MIT licensed.
A module for managing ES6 promise concurrency, frequency, and efficiency.
Fastest generic Pool written with TypeScript
MongoDB Server for testing (auto-download latest version). The server will allow you to connect your favourite ODM or client library to the MongoDB Server and run parallel integration tests isolated from each other.
A global, thread-safe memory pool.
A fixed-size, thread-safe memory pool allocator for Rust, supporting custom chunk sizes and efficient allocation/deallocation.
A fast and compact pool allocator with block sorting support.
A concurrent object pool.
Simple allocator for small copyable objects inspired by object-pools.
Lake is a high-octane memory pool with direct access, checkpoints, rollback, and zero-allocation droplets. No GC. No overhead. Just you and the bytes — total control. Allocate like a cyber-samurai.
Efficient memory pool with reference counting
LMAX inspired Lock-free ring buffers with cache-aligned memory pools for high-performance event systems
Stack for u8 slices in a client-provided buffers
Safe Rust wrappers for the CUDA Driver API (devices, contexts, streams, events, memory, kernels, graphs).
quickly and easily fork a pool of resque workers, saving memory (w/REE) and monitoring their uptime
Memory management (weak references and autorelease pools) for RubyMotion
quickly and easily fork a pool of qless workers, saving memory (w/REE) and monitoring their uptime
quickly and easily fork a pool of resque workers, saving memory (w/REE) and monitoring their uptime
quickly and easily fork a pool of resque workers, saving memory (w/REE) and monitoring their uptime
quickly and easily fork a pool of resque workers, saving memory (w/REE) and monitoring their uptime
RSpec and Cucumber DSL that allows definition of processes with their arguments, working directory, time outs, port numbers etc. and start/stop them during test runs. Processes with same definitions can be pooled and reused between example runs to save time on startup/shutdown. Pooling supports limiting the number of running processes with LRU to limit memory used.
RuPol is a glamorous mixin for instance pooling your Ruby classes. It eases the pain of garbarge collection for classes that are instantiated many times, and then tossed away like runway trash. Instances are cached on the class in a pool (array in less glamorous terms), and can be recycled at will. Of course there is no pain without gain, and models will trade collection costs for memory usages. The Swimsuit mixin edition overrides #new and #destroy, for a virtually pain free instance swimming experience. Runway not included.
A high-performance pure Ruby Red-Black Tree implementation. Features: O(1) key lookup via hybrid hash index, O(log n) insert/delete, lazy Enumerator-based range queries (lt/gt/between), nearest/prev/succ search, memory-efficient node pooling, and MultiRBTree for duplicate keys with first/last value access.
Provides RobotLab::RactorWorkerPool — a pool of Ruby Ractor workers for executing CPU-bound, Ractor-safe tools in parallel. Includes RactorBoundary (deep-freeze utility for crossing Ractor boundaries), RactorJob/RactorJobError/RobotSpec (frozen data carriers), RactorMemoryProxy (shared Memory access from inside Ractors), and RactorNetworkScheduler (dependency-ordered pipeline across Ractors).
ActiveMatrix is a comprehensive Rails-native Matrix SDK that enables developers to build sophisticated multi-agent bot systems and real-time communication features. This gem provides deep Rails integration with ActiveRecord models, state machines for bot lifecycle management, multi-tiered memory systems, intelligent event routing, connection pooling, and built-in inter-agent communication. Perfect for building chatbots, automation systems, monitoring agents, and collaborative AI systems within Rails applications. Features include command handling, room management, media support, end-to-end encryption capabilities, and extensive protocol support (CS, AS, IS, SS).
This is an experimental branch that implements a connection pool of Net::HTTP objects instead of a connection/thread. C/T is fine if you're only using your http threads to make connections but if you use them in child threads then I suspect you will have a thread memory leak. Also, I want to see if I get less connection resets if the most recently used connection is always returned. Also added a :force_retry option that if set to true will retry POST requests as well as idempotent requests. This branch is currently incompatible with the master branch in the following ways: * It doesn't allow you to recreate the Net::HTTP::Persistent object on the fly. This is possible in the master version since all the data is kept in thread local storage. For this version, you should probably create a class instance of the object and use that in your instance methods. * It uses a hash in the initialize method. This was easier for me as I use a HashWithIndifferentAccess created from a YAML file to define my options. This should probably be modified to check the arguments to achieve backwards compatibility. * The method shutdown is unimplemented as I wasn't sure how I should implement it and I don't need it as I do a graceful shutdown from nginx to finish up my connections. For connection issues, I completely recreate a new Net::HTTP instance. I was running into an issue which I suspect is a JRuby bug where an SSL connection that times out would leave the ssl context in a frozen state which would then make that connection unusable so each time that thread handled a connection a 500 error with the exception "TypeError: can't modify frozen". I think Joseph West's fork resolves this issue but I'm paranoid so I recreate the object. Compatibility with the master version could probably be achieved by creating a Strategy wrapper class for GenePool and a separate strategy class with the connection/thread implementation.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.