General criteria
A benchmark:
- Must be compile with a simple
npm|yarn|pnpm install and tsc -p or tsc -b. No funky build systems, no random external artifacts if possible.
- Compiling with
-p is preferred, to prevent fail-fast behavior.
- Emitting with tsc is even better. Especially declaration emit
- Should compile in less than 60 seconds or so. If you have a benchmark and it takes like 5 minutes to build, that deserves a bug!
Potential candidates
Pulling this list out of microsoft/TypeScript#44033
Being in this list does not guarantee that actually want to add the benchmarks, or that there aren't other benchmarks we could add.
Our benchmarking system uses tuned physical machines for accurate measurement, so benchmarking time is limited. More capacity is on the way, and removing our old legacy internal benchmarks will free up more time.
General criteria
A benchmark:
npm|yarn|pnpm installandtsc -portsc -b. No funky build systems, no random external artifacts if possible.-pis preferred, to prevent fail-fast behavior.Potential candidates
Pulling this list out of microsoft/TypeScript#44033
https://github.com/ChromeDevTools/devtools-frontendthis build is way too custom; tsconfigs do not actually buildBeing in this list does not guarantee that actually want to add the benchmarks, or that there aren't other benchmarks we could add.
Our benchmarking system uses tuned physical machines for accurate measurement, so benchmarking time is limited. More capacity is on the way, and removing our old legacy internal benchmarks will free up more time.