jest/benchmarks/test-file-overhead
Paul O’Shannessy 6d2632adae
Update copyrights with Meta Platforms, restore original license in Jasmine fork (#13879)
2023-02-09 08:13:08 +01:00
..
.gitignore perf(jest-runtime): load `chalk` only once per worker (#10864) 2021-02-11 09:20:10 +01:00
0.test.js Update copyrights with Meta Platforms, restore original license in Jasmine fork (#13879) 2023-02-09 08:13:08 +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 chore: update yarn (#12454) 2022-02-22 09:37:44 +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