From 450ec5c83b6d1c61352efa01775a0c57234d82c4 Mon Sep 17 00:00:00 2001 From: =?utf8?q?J=C3=A9r=C3=B4me=20Benoit?= Date: Fri, 22 Sep 2023 20:53:02 +0200 Subject: [PATCH] docs: fix benchmark links MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit Signed-off-by: Jérôme Benoit --- benchmarks/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/benchmarks/README.md b/benchmarks/README.md index 602b9e91..61d1cb98 100644 --- 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,7 +35,7 @@ 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 -- 2.34.1