jest/benchmarks/test-file-overhead
Tim Seckinger 42f78d4923
perf(jest-runtime): load `chalk` only once per worker (#10864)
2021-02-11 09:20:10 +01:00
..
.gitignore perf(jest-runtime): load `chalk` only once per worker (#10864) 2021-02-11 09:20:10 +01:00
0.test.js perf(jest-runtime): load `chalk` only once per worker (#10864) 2021-02-11 09:20:10 +01:00
README.md perf(jest-runtime): load `chalk` only once per worker (#10864) 2021-02-11 09:20:10 +01:00
package.json perf(jest-runtime): load `chalk` only once per worker (#10864) 2021-02-11 09:20:10 +01:00
prepare.sh perf(jest-runtime): load `chalk` only once per worker (#10864) 2021-02-11 09:20:10 +01:00
yarn.lock perf(jest-runtime): load `chalk` only once per worker (#10864) 2021-02-11 09:20:10 +01:00

README.md

First, run ./prepare.sh to generate the benchmark files. On Windows, use a Bash (WSL, Git, Cygwin …) to do this, but you can use CMD for the actual benchmark run if the CMD environment is what you want to benchmark for.

To run the benchmark, use a benchmarking tool such as hyperfine:

hyperfine -w 3 -m 10 ../../jest /tmp/other-jest-clone-to-compare-against/jest