Threadjs benchmarks (#230)

[poolifier.git] / README.md

diff --git a/README.md b/README.md
index 83ec2122c2bf11bc4aab12c28bf50676f88b5fcd..ce026b148412eb6e445db1b6d6f53775af7bed2d 100644 (file)
--- a/README.md
+++ b/README.md
@@ -3,6 +3,10 @@
 </div>
 
 <h2 align="center">Node Thread Pool and Cluster Pool :arrow_double_up: :on:</h2>
+<h2 align="center">
+  <a href="https://ko-fi.com/Q5Q31D6QY">
+    <img alt="Ko-fi" src="https://ko-fi.com/img/githubbutton_sm.svg"></a>
+</h2>
 
 <p align="center">
   <a href="https://www.npmjs.com/package/poolifier">
@@ -199,7 +203,9 @@ We already have a bench folder where you can find some comparisons.
 Thread pools are built on top of Node.js [worker-threads](https://nodejs.org/api/worker_threads.html#worker_threads_worker_threads) module.
 
 **Cluster pools** (FixedClusterPool and DynamicClusterPool) are suggested to run I/O intensive tasks, again you can still run CPU intensive tasks into cluster pools, but performance enhancement is expected to be minimal.  
-Cluster pools are built on top of Node.js [cluster](https://nodejs.org/api/cluster.html) module.
+Cluster pools are built on top of Node.js [cluster](https://nodejs.org/api/cluster.html) module.  
+
+**Remember** that some Node.js tasks are execute by Node.js into the libuv worker pool at process level as explained [here](https://nodejs.org/en/docs/guides/dont-block-the-event-loop/#what-code-runs-on-the-worker-pool).
 
 To choose your pool consider that with a FixedThreadPool/FixedClusterPool or a DynamicThreadPool/DynamicClusterPool (in this case is important the min parameter passed to the constructor) your application memory footprint will increase.  
 Increasing the memory footprint, your application will be ready to accept more tasks, but during idle time your application will consume more memory.