feat(scripts): allow filtering the benchmarks to run(#18557)

Merged
Merging
aqrln/bench-name
into
main
-15%
IMPROVEMENTS
0
REGRESSIONS
2
UNTOUCHED
1
NEW
0
DROPPED
0

Benchmarks

Failing

client generation ~50 Models
Regression
packages/client/src/__tests__/benchmarks/huge-schema/huge-schema.bench.ts::typescript::client generation ~50 Models
-12%
5.4 s
6.1 s
typescript compilation ~50 Models
Regression
packages/client/src/__tests__/benchmarks/huge-schema/huge-schema.bench.ts::typescript::typescript compilation ~50 Models
-15%
44.5 ms
52.1 ms

Passing

client generation 100 models with relations
packages/client/src/__tests__/benchmarks/lots-of-relations/lots-of-relations.bench.ts::typescript::client generation 100 models with relations
+2%
61.4 s
60.1 s

Commits

Click on a commit to change the comparison range
chore(bench): fix benchmark GH action on main (#18463) Currently the "Store benchmark result" step of the benchmark pipeline fails with `Error: No benchmark result was found in /home/runner/work/prisma/prisma/output.txt.`. The reason is the second benchmark run overwrites the `output.txt` file from the first run but doesn't contain the raw Benchmark.js output. This commit fixes that.
base
b990cf0
8 months ago by aqrln
-15%
feat(scripts): allow filtering the benchmarks to run Make it possible to run a single benchmark or a subset of benchmarks by specifying a name pattern, similar to Jest tests.
1a4d026
8 months ago by aqrln
ResourcesHomePricingDocsBlogGitHub
Copyright © 2023 CodSpeed Technology SAS. All rights reserved.