@@ -22,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](https://github.com/poolifier/benchmark/BENCH-100000.md).
+ - CPU Intensive task with 100k operations submitted to each pool: [https://bencher.dev/perf/poolifier-benchmark](https://bencher.dev/perf/poolifier-benchmark).
- External pools with which we used to compare the poolifier results:
- 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**
> :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
## 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`.