chore: v3.0.5

[poolifier.git] / benchmarks / README.md

diff --git a/benchmarks/README.md b/benchmarks/README.md
index d217c260eef641113642813d3f6e9349ba0be671..ca2b0667e86e35f34fd8d4f6c70f4456451bbe62 100644 (file)
--- a/benchmarks/README.md
+++ b/benchmarks/README.md
@@ -1,13 +1,12 @@
-# Poolifier Benchmarks
+# Poolifier benchmarks

 
 Welcome to poolifier benchmarks and thanks to look into this project.
 
 ## Folder Structure
 
 
 Welcome to poolifier benchmarks and thanks to look into this project.
 
 ## Folder Structure
 

-The [internal](./internal) folder contains poolifier internal benchmark.  
-The [versus-external-pools](./versus-external-pools) folder contains benchmark versus other Node.js pools.
+The [internal](./internal) folder contains poolifier internal benchmark.

 
 

-## Poolifier vs other pools benchmark
+## Poolifier benchmark versus other worker pools

 
 To compare poolifier pools performance vs other pools performance we chose to use [hyperfine](https://github.com/sharkdp/hyperfine).  
 We chose to use this tool because it allows to run isolated Node.js processes so each pool does not impact each other.
 
 To compare poolifier pools performance vs other pools performance we chose to use [hyperfine](https://github.com/sharkdp/hyperfine).  
 We chose to use this tool because it allows to run isolated Node.js processes so each pool does not impact each other.


@@ -23,7 +22,7 @@ We chose to use this tool because it allows to run isolated Node.js processes so
 
   Those are our results:
 
 
   Those are our results:
 

-  - CPU Intensive task with 100k operations submitted to each pool: [BENCH-100000.md](./versus-external-pools/BENCH-100000.md).
+  - CPU Intensive task with 100k operations submitted to each pool: [https://poolifier.github.io/benchmark](https://poolifier.github.io/benchmark).

 
 - External pools with which we used to compare the poolifier results:
 
 
 - External pools with which we used to compare the poolifier results:
 


@@ -32,18 +31,16 @@ We chose to use this tool because it allows to run isolated Node.js processes so
   - [worker-threads-pool](https://github.com/watson/worker-threads-pool): removed because unmaintained since more than 4 years.
   - [threadwork](https://github.com/kevlened/threadwork): removed because unmaintained since more than 3 years.
   - [microjob](https://github.com/wilk/microjob): removed because unmaintained since more than 5 years.
   - [worker-threads-pool](https://github.com/watson/worker-threads-pool): removed because unmaintained since more than 4 years.
   - [threadwork](https://github.com/kevlened/threadwork): removed because unmaintained since more than 3 years.
   - [microjob](https://github.com/wilk/microjob): removed because unmaintained since more than 5 years.

-  - [threads.js](https://github.com/andywer/threads.js/): removed because not a threads pool.
+  - [threads.js](https://github.com/andywer/threads.js): removed because not a threads pool.

 
 > :warning: **We would need funds to run our benchmark more often and on Cloud VMs, please consider to sponsor this project**
 
 
 > :warning: **We would need funds to run our benchmark more often and on Cloud VMs, please consider to sponsor this project**
 

-Read the [README.md](./versus-external-pools/README.md) to know how to run the benchmark.
+Read the [README.md](https://github.com/poolifier/benchmark#readme) to know how to run the benchmark.

 
 ## Poolifier internal benchmark
 
 ### Usage
 
 
 ## Poolifier internal benchmark
 
 ### Usage
 

-To run the internal benchmark, you just need to navigate to the root of poolifier project and run `pnpm benchmark`
+To run the internal benchmark, you just need to navigate to the root of poolifier cloned repository and run `pnpm benchmark`.

 
 

-### Results
-
-[Continuous internal benchmark result](https://poolifier.github.io/benchmark-results/dev/bench)
+### [Results](https://bencher.dev/perf/poolifier)