script-pool v1.0.9
script-pool
implementation of fork and cluster modes for the generic-poolhttps://github.com/coopernurse/node-pool#readme package.
worker.js
process.on('message', (msg) => {
setTimeout(() => {
process.send(msg);
}, Math.ceil(Math.random() * 100) + 1);
});
cluster pool
const { createClusterPool } = require("script-pool");
const pool = await createClusterPool({
min: 2, // min number of workers
max: 8, // max number of workers
autostart: false,
}, 'worker.js');
await pool.start();
await instance = pool.acquire();
// do stuff like
/*instance.once("message", (answer)=>{
// do something with answer
});
instance.send(msg);*/
// then release
await pool.release(instance);
// await pool.drain();
// await pool.clear();
fork pool
const { createForkPool } = require("script-pool");
const pool = await createClusterPool({
min: 2, // min number of workers
max: 8, // max number of workers
autostart: false,
}, 'worker.js');
await pool.start();
await instance = pool.acquire();
// do stuff like
/*instance.once("message", (answer)=>{
// do something with answer
});
instance.send(msg);*/
// then release
await pool.release(instance);
// await pool.drain();
// await pool.clear();
see generic-poolhttps://github.com/coopernurse/node-pool#readme for more options.
documentation
IMPORTANTE NOTICE
Following text taken from the generic-pool readme.md
see generic-poolhttps://github.com/coopernurse/node-pool#readme for more information.
opts
An optional object/dictionary with the any of the following properties:
max
: maximum number of resources to create at any given time. (default=1)min
: minimum number of resources to keep in pool at any given time. If this is set >= max, the pool will silently set the min to equalmax
. (default=0)maxWaitingClients
: maximum number of queued requests allowed, additionalacquire
calls will be callback with anerr
in a future cycle of the event loop.testOnBorrow
:boolean
: should the pool validate resources before giving them to clients. Requires thatfactory.validate
is specified.acquireTimeoutMillis
: max milliseconds anacquire
call will wait for a resource before timing out. (default no limit), if supplied should non-zero positive integer.fifo
: if true the oldest resources will be first to be allocated. If false the most recently released resources will be the first to be allocated. This in effect turns the pool's behaviour from a queue into a stack.boolean
, (default true)priorityRange
: int between 1 and x - if set, borrowers can specify their relative priority in the queue if no resources are available. see example. (default 1)autostart
: boolean, should the pool start creating resources, initialize the evictor, etc once the constructor is called. If false, the pool can be started by callingpool.start
, otherwise the first call toacquire
will start the pool. (default true)evictionRunIntervalMillis
: How often to run eviction checks. Default: 0 (does not run).numTestsPerEvictionRun
: Number of resources to check each eviction run. Default: 3.softIdleTimeoutMillis
: amount of time an object may sit idle in the pool before it is eligible for eviction by the idle object evictor (if any), with the extra condition that at least "min idle" object instances remain in the pool. Default -1 (nothing can get evicted)idleTimeoutMillis
: the minimum amount of time that an object may sit idle in the pool before it is eligible for eviction due to idle time. SupercedessoftIdleTimeoutMillis
Default: 30000Promise
: Promise lib, a Promises/A+ implementation that the pool should use. Defaults to whateverglobal.Promise
is (usually native promises).
pool.acquire
const onfulfilled = function(resource){
resource.doStuff()
// release/destroy/etc
}
pool.acquire().then(onfulfilled)
//or
const priority = 2
pool.acquire(priority).then(onfulfilled)
This function is for when you want to "borrow" a resource from the pool.
acquire
takes one optional argument:
priority
: optional, number, see Priority Queueing below.
and returns a Promise
Once a resource in the pool is available, the promise will be resolved with a resource
(whatever factory.create
makes for you). If the Pool is unable to give a resource (e.g timeout) then the promise will be rejected with an Error
pool.release
pool.release(resource)
This function is for when you want to return a resource to the pool.
release
takes one required argument:
resource
: a previously borrowed resource
and returns a Promise
. This promise will resolve once the resource
is accepted by the pool, or reject if the pool is unable to accept the resource
for any reason (e.g resource
is not a resource or object that came from the pool). If you do not care the outcome it is safe to ignore this promise.
pool.isBorrowedResource
pool.isBorrowedResource(resource)
This function is for when you need to check if a resource has been acquired from the pool and not yet released/destroyed.
isBorrowedResource
takes one required argument:
resource
: any object which you need to test
and returns true (primitive, not Promise) if resource is currently borrowed from the pool, false otherwise.
pool.destroy
pool.destroy(resource)
This function is for when you want to return a resource to the pool but want it destroyed rather than being made available to other resources. E.g you may know the resource has timed out or crashed.
destroy
takes one required argument:
resource
: a previously borrowed resource
and returns a Promise
. This promise will resolve once the resource
is accepted by the pool, or reject if the pool is unable to accept the resource
for any reason (e.g resource
is not a resource or object that came from the pool). If you do not care the outcome it is safe to ignore this promise.
pool.on
pool.on('factoryCreateError', function(err){
//log stuff maybe
})
pool.on('factoryDestroyError', function(err){
//log stuff maybe
})
The pool is an event emitter. Below are the events it emits and any args for those events
factoryCreateError
: emitted when a promise returned byfactory.create
is rejected. If this event has no listeners then theerror
will be silently discardederror
: whateverreason
the promise was rejected with.
factoryDestroyError
: emitted when a promise returned byfactory.destroy
is rejected. If this event has no listeners then theerror
will be silently discardederror
: whateverreason
the promise was rejected with.
pool.start
pool.start()
If autostart
is false
then this method can be used to start the pool and therefore begin creation of resources, start the evictor, and any other internal logic.
pool.use
const myTask = dbClient => {
return new Promise( (resolve, reject) => {
// do something with the client and resolve/reject
})
}
pool.use(myTask).then(/* a promise that will run after myTask resolves */)
This method handles acquiring a resource
from the pool, handing it to your function and then calling pool.release
or pool.destroy
with resource after your function has finished.
use
takes one required argument:
fn
: a function that accepts aresource
and returns aPromise
. Once that promiseresolve
s theresource
is returned to the pool, else if itreject
s then the resource is destroyed.
and returns a Promise
that either resolve
s with the value from the user supplied fn
or reject
s with an error.
Idle Object Eviction
The pool has an evictor (off by default) which will inspect idle items in the pool and destroy
them if they are too old.
By default the evictor does not run, to enable it you must set the evictionRunIntervalMillis
option to a non-zero value. Once enable the evictor will check at most numTestsPerEvictionRun
each time, this is to stop it blocking your application if you have lots of resources in the pool.
Priority Queueing
The pool supports optional priority queueing. This becomes relevant when no resources are available and the caller has to wait. acquire()
accepts an optional priority int which
specifies the caller's relative position in the queue. Each priority slot has it's own internal queue created for it. When a resource is available for borrowing, the first request in the highest priority queue will be given it.
Specifying a priority
to acquire
that is outside the priorityRange
set at Pool
creation time will result in the priority
being converted the lowest possible priority
// create pool with priorityRange of 3
// borrowers can specify a priority 0 to 2
const opts = {
priorityRange : 3
}
const pool = genericPool.createPool(someFactory,opts);
// acquire connection - no priority specified - will go onto lowest priority queue
pool.acquire().then(function(client) {
pool.release(client);
});
// acquire connection - high priority - will go into highest priority queue
pool.acquire(0).then(function(client) {
pool.release(client);
});
// acquire connection - medium priority - will go into 'mid' priority queue
pool.acquire(1).then(function(client) {
pool.release(client);
});
// etc..
Draining
If you are shutting down a long-lived process, you may notice that node fails to exit for 30 seconds or so. This is a side effect of the idleTimeoutMillis behavior -- the pool has a setTimeout() call registered that is in the event loop queue, so node won't terminate until all resources have timed out, and the pool stops trying to manage them.
This behavior will be more problematic when you set factory.min > 0, as the pool will never become empty, and the setTimeout calls will never end.
In these cases, use the pool.drain() function. This sets the pool into a "draining" state which will gracefully wait until all idle resources have timed out. For example, you can call:
If you do this, your node process will exit gracefully.
If you know you would like to terminate all the available resources in your pool before any timeouts they might have are reached, you can use clear()
in conjunction with drain()
:
const p = pool.drain()
.then(function() {
return pool.clear();
});
The promise
returned will resolve once all waiting clients have acquired and return resources, and any available resources have been destroyed
One side-effect of calling drain()
is that subsequent calls to acquire()
will throw an Error.
Pooled function decoration
This has now been extracted out it's own module generic-pool-decorator
Pool info
The following properties will let you get information about the pool:
// How many many more resources can the pool manage/create
pool.spareResourceCapacity
// returns number of resources in the pool regardless of
// whether they are free or in use
pool.size
// returns number of unused resources in the pool
pool.available
// number of resources that are currently acquired by userland code
pool.borrowed
// returns number of callers waiting to acquire a resource
pool.pending
// returns number of maxixmum number of resources allowed by pool
pool.max
// returns number of minimum number of resources allowed by pool
pool.min