Make any web worker.js could run as normal function in main thread.
Offload tasks to a pool of workers on node.js and in the browser
No description provided.
A mutex for guarding async workflows
Seamless REST/GraphQL API mocking library for browser and Node.js.
Consistent Web Workers in browser and Node.
Utilities for executing code in Web Workers
A fast, efficient Node.js Worker Thread Pool implementation
The worker which is used by the worker-timers package.
Communicate with a Web Worker using Promises, allowing transferList
A little factory function to create a JSON-RPC based Web Worker implementation.
Temporal.io SDK Worker sub-package
worker loader module for webpack
Distribute processing tasks to child processes with an über-simple API and baked-in durability & custom concurrency options.
The broker which is used by the worker-timers package.
Client Server RPC worker for CSpell.
A simple RPC layer for communicating with web workers and over other transports
Consistent Web Workers in browser and Node.
A Node.js communication port that can pass messages synchronously between workers
A minimal and tiny Node.js Worker Thread Pool implementation, a fork of piscina, but with fewer features
A high-performance pure-javascript SHA1 implementation suitable for large binary data.
Fast, in memory work queue
A replacement for setInterval() and setTimeout() which works in unfocused windows.
Web workers & worker threads as simple as a function call
Non-blocking thread-pool based workers for blocking operations.
Handles your HTTP requests in background in non-blocking way using Resque worker
Em-resque is a version of Resque, which offers non-blocking and non-forking workers. The idea is to have fast as possible workers for tasks with lots of IO like pinging third party servers or hitting the database. The async worker is using fibers through Synchrony library to reduce the amount of callback functions. There's one fiber for worker and if one of the workers is blocking, it will block all the workers at the same time. The idea to use this version and not the regular Resque is to reduce the amount of SQL connections for high-load services. Using one process for many workers gives a better control to the amount of SQL connections. For using Resque please refer the original project. https://github.com/defunkt/resque/ The library adds two rake tasks over Resque: * resque:work_async for working inside the EventMachine
Fire and Forget replaces the need to write resque tasks or delayed jobs to fire off web requests (usually notification webhooks or a anti-spam service, like defensio or akismet). A single worker reads and executes web requests from a blocking named pipe, while clients queue up them up in a non blocking manner. It uses typhoeus internally to execute the web requests for maximum speed.
No description provided.
No description provided.
No description provided.
No description provided.