chore: v3.0.5

[poolifier.git] / benchmarks / README.md

diff --git a/benchmarks/README.md b/benchmarks/README.md
index 602b9e916163e1d7339fea2781f0c955046d1c19..ca2b0667e86e35f34fd8d4f6c70f4456451bbe62 100644 (file)
--- a/benchmarks/README.md
+++ b/benchmarks/README.md
@@ -22,7 +22,7 @@ We chose to use this tool because it allows to run isolated Node.js processes so
 
   Those are our results:
 
-  - CPU Intensive task with 100k operations submitted to each pool: [BENCH-100000.md](https://github.com/poolifier/benchmark/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:
 
@@ -35,12 +35,12 @@ We chose to use this tool because it allows to run isolated Node.js processes so
 
 > :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](https://github.com/poolifier/benchmark#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
 
-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](https://poolifier.github.io/benchmark-results/dev/bench)
+### [Results](https://bencher.dev/perf/poolifier)