Tinypool - the node.js worker pool ๐งต
Piscina: A fast, efficient Node.js Worker Thread Pool implementation
Tinypool is a fork of piscina. What we try to achieve in this library, is to eliminate some dependencies and features that our target users don't need (currently, our main user will be Vitest). Tinypool's install size (38KB) can then be smaller than Piscina's install size (6MB). If you need features like utilization or NAPI, Piscina is a better choice for you. We think that Piscina is an amazing library, and we may try to upstream some of the dependencies optimization in this fork.
-
โ Smaller install size, 38KB
-
โ Minimal
-
โ No dependencies
-
โ Physical cores instead of Logical cores with physical-cpu-count
-
โ Supports
worker_threads
andchild_process
-
โ No utilization
-
โ No NAPI
-
Written in TypeScript, and ESM support only. For Node.js 18.x and higher.
In case you need more tiny libraries like tinypool or tinyspy, please consider submitting an RFC
Example
Using node:worker_threads
Basic usage
// main.mjs
import Tinypool from 'tinypool'
const pool = new Tinypool({
filename: new URL('./worker.mjs', import.meta.url).href,
})
const result = await pool.run({ a: 4, b: 6 })
console.log(result) // Prints 10
// Make sure to destroy pool once it's not needed anymore
// This terminates all pool's idle workers
await pool.destroy()
// worker.mjs
export default ({ a, b }) => {
return a + b
}
Main thread <-> worker thread communication
See code
// main.mjs
import Tinypool from 'tinypool'
import { MessageChannel } from 'node:worker_threads'
const pool = new Tinypool({
filename: new URL('./worker.mjs', import.meta.url).href,
})
const { port1, port2 } = new MessageChannel()
const promise = pool.run({ port: port1 }, { transferList: [port1] })
port2.on('message', (message) => console.log('Main thread received:', message))
setTimeout(() => port2.postMessage('Hello from main thread!'), 1000)
await promise
port1.close()
port2.close()
// worker.mjs
export default ({ port }) => {
return new Promise((resolve) => {
port.on('message', (message) => {
console.log('Worker received:', message)
port.postMessage('Hello from worker thread!')
resolve()
})
})
}
Using node:child_process
Basic usage
See code
// main.mjs
import Tinypool from 'tinypool'
const pool = new Tinypool({
runtime: 'child_process',
filename: new URL('./worker.mjs', import.meta.url).href,
})
const result = await pool.run({ a: 4, b: 6 })
console.log(result) // Prints 10
// worker.mjs
export default ({ a, b }) => {
return a + b
}
Main process <-> worker process communication
See code
// main.mjs
import Tinypool from 'tinypool'
const pool = new Tinypool({
runtime: 'child_process',
filename: new URL('./worker.mjs', import.meta.url).href,
})
const messages = []
const listeners = []
const channel = {
onMessage: (listener) => listeners.push(listener),
postMessage: (message) => messages.push(message),
}
const promise = pool.run({}, { channel })
// Send message to worker
setTimeout(
() => listeners.forEach((listener) => listener('Hello from main process')),
1000
)
// Wait for task to finish
await promise
console.log(messages)
// [{ received: 'Hello from main process', response: 'Hello from worker' }]
// worker.mjs
export default async function run() {
return new Promise((resolve) => {
process.on('message', (message) => {
// Ignore Tinypool's internal messages
if (message?.__tinypool_worker_message__) return
process.send({ received: message, response: 'Hello from worker' })
resolve()
})
})
}
API
We have a similar API to Piscina, so for more information, you can read Piscina's detailed documentation and apply the same techniques here.
Tinypool specific APIs
Pool constructor options
isolateWorkers
: Disabled by default. Always starts with a fresh worker when running tasks to isolate the environment.terminateTimeout
: Disabled by default. If terminating a worker takesterminateTimeout
amount of milliseconds to execute, an error is raised.maxMemoryLimitBeforeRecycle
: Disabled by default. When defined, the worker's heap memory usage is compared against this value after task has been finished. If the current memory usage exceeds this limit, worker is terminated and a new one is started to take its place. This option is useful when your tasks leak memory and you don't want to enableisolateWorkers
option.runtime
: Used to pick worker runtime. Default value isworker_threads
.worker_threads
: Runs workers innode:worker_threads
. Formain thread <-> worker thread
communication you can useMessagePort
in thepool.run()
method'stransferList
option. See example.child_process
: Runs workers innode:child_process
. Formain thread <-> worker process
communication you can useTinypoolChannel
in thepool.run()
method'schannel
option. For filtering out the Tinypool's internal messages seeTinypoolWorkerMessage
. See example.
Pool methods
cancelPendingTasks()
: Gracefully cancels all pending tasks without stopping or interfering with on-going tasks. This method is useful when your tasks may have side effects and should not be terminated forcefully during task execution. If your tasks don't have any side effects you may want to use{ signal }
option for forcefully terminating all tasks, including the on-going ones, instead.recycleWorkers(options)
: Waits for all current tasks to finish and re-creates all workers. Can be used to force isolation imperatively even whenisolateWorkers
is disabled. Accepts{ runtime }
option as argument.
Exports
workerId
: Each worker now has an id ( <=maxThreads
) that can be imported fromtinypool
in the worker itself (orprocess.__tinypool_state__.workerId
).
Authors
Mohammad Bagher |
---|
Sponsors
Your sponsorship can make a huge difference in continuing our work in open source!
Credits
The Vitest team for giving me the chance of creating and maintaing this project for vitest.
Piscina, because Tinypool is not more than a friendly fork of piscina.