From: Jérôme Benoit Date: Sat, 15 Jul 2023 14:01:41 +0000 (+0200) Subject: docs: fix README.md X-Git-Tag: v2.6.17~6 X-Git-Url: https://git.piment-noir.org/?a=commitdiff_plain;h=43b84974f72aecd75b4b592e0009359bd5baf228;p=poolifier.git docs: fix README.md Signed-off-by: Jérôme Benoit --- diff --git a/README.md b/README.md index 4b153dcd..6e6e46fb 100644 --- a/README.md +++ b/README.md @@ -80,7 +80,7 @@ Please consult our [general guidelines](#general-guidance). ## Overview -Poolifier contains two [worker_threads](https://nodejs.org/api/worker_threads.html#class-worker)/[cluster](https://nodejs.org/api/cluster.html#cluster_class_worker) worker pool implementations, you don't have to deal with worker\*threads/cluster complexity. +Poolifier contains two [worker_threads](https://nodejs.org/api/worker_threads.html#class-worker)/[cluster](https://nodejs.org/api/cluster.html#cluster_class_worker) worker pool implementations, you don't have to deal with worker_threads/cluster complexity. The first implementation is a static worker pool, with a defined number of workers that are started at creation time and will be reused. The second implementation is a dynamic worker pool with a number of worker started at creation time (these workers will be always active and reused) and other workers created when the load will increase (with an upper limit, these workers will be reused when active), the new created workers will be stopped after a configurable period of inactivity. You have to implement your worker by extending the _ThreadWorker_ or _ClusterWorker_ class.