Update README.md
[poolifier.git] / README.md
CommitLineData
987e0026 1# Node Thread Pool :arrow_double_up: :on:
50aa7901 2
34a572eb 3[![JavaScript Style Guide](https://img.shields.io/badge/code_style-standard-brightgreen.svg)](https://standardjs.com)
103df814 4[![Dependabot](https://badgen.net/dependabot/dependabot/dependabot-core/?icon=dependabot)](https://badgen.net/dependabot/dependabot/dependabot-core/?icon=dependabot)
58a76e22 5[![npm w](https://img.shields.io/npm/dw/poolifier)](https://www.npmjs.com/package/poolifier)
e7752b74 6[![Actions Status](https://github.com/pioardi/node-pool/workflows/NodeCI/badge.svg)](https://github.com/pioardi/node-pool/actions)
ddaa3a76 7[![Quality Gate Status](https://sonarcloud.io/api/project_badges/measure?project=pioardi_poolifier&metric=alert_status)](https://sonarcloud.io/dashboard?id=pioardi_poolifier)
7e04d52e 8 [![SonarCloud Coverage](https://sonarcloud.io/api/project_badges/measure?project=pioardi_poolifier&metric=coverage)](https://sonarcloud.io/component_measures/metric/coverage/list?id=pioardi_poolifier)
50aa7901
S
9[![PRs Welcome](https://img.shields.io/badge/PRs-welcome-brightgreen.svg?style=flat-square)](http://makeapullrequest.com)
10[![NODEP](https://img.shields.io/static/v1?label=dependencies&message=no%20dependencies&color=brightgreen)](https://img.shields.io/static/v1?label=dependencies&message=no%20dependencies&color=brightgreen)
6ba2673b 11[![Gitter](https://badges.gitter.im/poolifier/community.svg)](https://gitter.im/poolifier/community?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge)
b4b2dc8b 12
f2b5671a
APA
13<div align="center">
14<img src="./docs/logo.png" width="250" height="300"/>
ddaa3a76 15</div>
16
50aa7901 17## Why Poolifier?
e76f5485 18
50aa7901
S
19Poolifier is used to perform heavy CPU bound tasks on nodejs servers, it implements thread pools (yes, more thread pool implementations, so you can choose which one fit better for you) using [worker-threads](https://nodejs.org/api/worker_threads.html#worker_threads_worker_threads).
20With poolifier you can improve your **performance** and resolve problems related to the event loop.
21Moreover you can execute your CPU tasks using an API designed to improve the **developer experience**.
e76f5485 22
ddaa3a76 23- Performance :racehorse:
f2b5671a 24- Security :bank: :cop: [![Security Rating](https://sonarcloud.io/api/project_badges/measure?project=pioardi_poolifier&metric=security_rating)](https://sonarcloud.io/dashboard?id=pioardi_poolifier) [![Vulnerabilities](https://sonarcloud.io/api/project_badges/measure?project=pioardi_poolifier&metric=vulnerabilities)](https://sonarcloud.io/dashboard?id=pioardi_poolifier)
ddaa3a76 25
f2b5671a 26- No runtime dependencies :heavy_check_mark: (until now we don't have any expectations to add some)- Easy to use :couple:
ddaa3a76 27- Code quality :octocat: [![Bugs](https://sonarcloud.io/api/project_badges/measure?project=pioardi_poolifier&metric=bugs)](https://sonarcloud.io/dashboard?id=pioardi_poolifier)
28[![Code Smells](https://sonarcloud.io/api/project_badges/measure?project=pioardi_poolifier&metric=code_smells)](https://sonarcloud.io/dashboard?id=pioardi_poolifier)
29[![Duplicated Lines (%)](https://sonarcloud.io/api/project_badges/measure?project=pioardi_poolifier&metric=duplicated_lines_density)](https://sonarcloud.io/dashboard?id=pioardi_poolifier)
30[![Maintainability Rating](https://sonarcloud.io/api/project_badges/measure?project=pioardi_poolifier&metric=sqale_rating)](https://sonarcloud.io/dashboard?id=pioardi_poolifier)
31[![Reliability Rating](https://sonarcloud.io/api/project_badges/measure?project=pioardi_poolifier&metric=reliability_rating)](https://sonarcloud.io/dashboard?id=pioardi_poolifier)
32[![Technical Debt](https://sonarcloud.io/api/project_badges/measure?project=pioardi_poolifier&metric=sqale_index)](https://sonarcloud.io/dashboard?id=pioardi_poolifier)
e628498e 33- Easy switch from a pool to another, easy to tune
ddaa3a76 34- Dynamic pool size
35- Proper async integration with node async hooks
36- Support for worker threads and cluster node modules
37- Active community
38- Support sync and async tasks
39- General guidance on pools to use
40- Widely tested
41- Error handling out of the box
42
50aa7901 43## Contents
e76f5485 44
34a572eb 45<h3 align="center">
50aa7901
S
46 <a href="#overview">Overview</a>
47 <span> · </span>
34a572eb 48 <a href="#installation">Installation</a>
49 <span> · </span>
50 <a href="#usage">Usage</a>
51 <span> · </span>
50aa7901
S
52 <a href="#node-versions"> Node versions</a>
53 <span> · </span>
34a572eb 54 <a href="#api">API</a>
55 <span> · </span>
50aa7901 56 <a href="#choose-your-pool">Choose your pool</a>
48211d04 57 <span> · </span>
34a572eb 58 <a href="#contribute">Contribute</a>
59 <span> · </span>
50aa7901 60 <a href="#team">Team</a>
34a572eb 61 <span> · </span>
62 <a href="#license">License</a>
63</h3>
64
50aa7901 65## Overview
13031992 66
50aa7901
S
67Node pool contains two [worker-threads](https://nodejs.org/api/worker_threads.html#worker_threads_worker_threads) pool implementations, you don't have to deal with worker-threads complexity.
68The first implementation is a static thread pool, with a defined number of threads that are started at creation time and will be reused.
69The second implementation is a dynamic thread pool with a number of threads started at creation time (these threads will be always active and reused) and other threads created when the load will increase (with an upper limit, these threads will be reused when active), the new created threads will be stopped after a configurable period of inactivity.
70You have to implement your worker extending the ThreadWorker class
71
72## Installation
73
74```shell
27c5fb75 75npm install poolifier --save
1a4ec243 76```
1a4ec243 77
50aa7901
S
78## Usage
79
80You can implement a worker in a simple way, extending the class ThreadWorker:
1a4ec243
APA
81
82```js
83'use strict'
d2eb4964 84const { ThreadWorker } = require('poolifier')
1a4ec243 85
106744f7 86function yourFunction (data) {
87 // this will be executed in the worker thread,
88 // the data will be received by using the execute method
89 return { ok: 1 }
90}
91
50aa7901
S
92module.exports = new ThreadWorker(yourFunction, {
93 maxInactiveTime: 60000,
94 async: false
95})
1a4ec243
APA
96```
97
1f9a5a44 98Instantiate your pool based on your needed :
1a4ec243
APA
99
100```js
101'use strict'
d2eb4964 102const { FixedThreadPool, DynamicThreadPool } = require('poolifier')
1a4ec243
APA
103
104// a fixed thread pool
105const pool = new FixedThreadPool(15,
106744f7 106 './yourWorker.js',
107 { errorHandler: (e) => console.error(e), onlineHandler: () => console.log('worker is online') })
1a4ec243
APA
108
109// or a dynamic thread pool
110const pool = new DynamicThreadPool(10, 100,
106744f7 111 './yourWorker.js',
112 { errorHandler: (e) => console.error(e), onlineHandler: () => console.log('worker is online') })
113
1a4ec243
APA
114pool.emitter.on('FullPool', () => console.log('Pool is full'))
115
116// the execute method signature is the same for both implementations,
117// so you can easy switch from one to another
118pool.execute({}).then(res => {
119 console.log(res)
777b7824 120}).catch ....
1a4ec243
APA
121
122```
123
50aa7901
S
124**See examples folder for more details (in particular if you want to use a pool for [multiple functions](./examples/multiFunctionExample.js)).**
125**Now type script is also supported, find how to use it into the example folder**
1a4ec243 126
50aa7901 127## Node versions
34a572eb 128
50aa7901 129You can use node versions 12.x, 13.x, 14.x
1a4ec243 130
50aa7901 131## API
34a572eb 132
133### `pool = new FixedThreadPool(numThreads, filePath, opts)`
50aa7901
S
134
135`numThreads` (mandatory) Num of threads for this worker pool
136`filePath` (mandatory) Path to a file with a worker implementation
34a572eb 137`opts` (optional) An object with these properties :
50aa7901 138
34a572eb 139- `errorHandler` - A function that will listen for error event on each worker thread
140- `onlineHandler` - A function that will listen for online event on each worker thread
141- `exitHandler` - A function that will listen for exit event on each worker thread
50aa7901 142- `maxTasks` - This is just to avoid not useful warnings message, is used to set [maxListeners](https://nodejs.org/dist/latest-v12.x/docs/api/events.html#events_emitter_setmaxlisteners_n) on event emitters (workers are event emitters)
34a572eb 143
144### `pool = new DynamicThreadPool(min, max, filePath, opts)`
50aa7901
S
145
146`min` (mandatory) Same as FixedThreadPool numThreads, this number of threads will be always active
147`max` (mandatory) Max number of workers that this pool can contain, the new created threads will die after a threshold (default is 1 minute, you can override it in your worker implementation).
148`filePath` (mandatory) Same as FixedThreadPool
149`opts` (optional) Same as FixedThreadPool
34a572eb 150
151### `pool.execute(data)`
50aa7901
S
152
153Execute method is available on both pool implementations (return type : Promise):
154`data` (mandatory) An object that you want to pass to your worker implementation
34a572eb 155
156### `pool.destroy()`
34a572eb 157
50aa7901
S
158Destroy method is available on both pool implementations.
159This method will call the terminate method on each worker.
34a572eb 160
161### `class YourWorker extends ThreadWorker`
50aa7901
S
162
163`fn` (mandatory) The function that you want to execute on the worker thread
164`opts` (optional) An object with these properties:
165
34a572eb 166- `maxInactiveTime` - Max time to wait tasks to work on ( in ms) , after this period the new worker threads will die.
50aa7901
S
167- `async` - true/false, true if your function contains async pieces else false
168
169## Choose your pool
34a572eb 170
50aa7901 171Performance is one of the main target of these thread pool implementations, we want to have a strong focus on this.
48211d04 172We already have a bench folder where you can find some comparisons.
50aa7901
S
173To choose your pool consider that with a FixedThreadPool or a DynamicThreadPool (in this case is important the min parameter passed to the constructor) your application memory footprint will increase.
174Increasing the memory footprint, your application will be ready to accept more CPU bound tasks, but during idle time your application will consume more memory.
175One good choose from my point of view is to profile your application using Fixed/Dynamic thread pool, and to see your application metrics when you increase/decrease the num of threads.
176For example you could keep the memory footprint low choosing a DynamicThreadPool with 5 threads, and allow to create new threads until 50/100 when needed, this is the advantage to use the DynamicThreadPool.
177But in general, **always profile your application**
48211d04 178
50aa7901 179## Contribute
34a572eb 180
50aa7901
S
181See guidelines [CONTRIBUTING](CONTRIBUTING.md)
182Choose your task here [2.0.0](https://github.com/pioardi/poolifier/projects/1), propose an idea, a fix, an improvement.
1a4ec243 183
50aa7901 184## Team
1a4ec243 185
39deb558 186<!-- ALL-CONTRIBUTORS-LIST:START - Do not remove or modify this section -->
187<!-- prettier-ignore-start -->
188<!-- markdownlint-disable -->
189
190**Creator/Owner:**
39deb558 191
50aa7901
S
192- [**Alessandro Pio Ardizio**](https://github.com/pioardi)
193
194**_Contributors_**
195
196- [**Shinigami92**](https://github.com/Shinigami92)
197- [**Jérôme Benoit**](https://github.com/jerome-benoit)
39deb558 198
50aa7901 199## License
1a4ec243 200
9507c1d4 201[MIT](./LICENSE)