William Hesse
84f9338346
The Windows builder analyzer-win-release is waiting for shards to complete after running the analysis server benchmarks, so we can run the benchmarks twice to get more better results. Bug: b/74375756 Change-Id: I03f459aece293a7e0b0eed3f4c52c037e2d9641c Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/290061 Reviewed-by: Alexander Thomas <athom@google.com>
Analysis Server Benchmarks
How to run the benchmarks
To see a list of all available benchmarks, run:
dart benchmark/benchmarks.dart list
To run an individual benchmark, run:
dart benchmark/benchmarks.dart run <benchmark-id>
How they're tested
In order to make sure that our benchmarks don't regress in terms of their ability to run, we create one unit test per benchmark, and run those tests as part of our normal CI test suite.
To save time on the CI, we only run one iteration of each benchmark
(--repeat=1), and we run the benchmark on a smaller data set (--quick).
See test/benchmark_test.dart.
To add a new benchmark
Register the new benchmark in the main() method of benchmark/benchmarks.dart.
On the bots
Our benchmarks run on a continuous performance testing system. Currently, the benchmarks need to be manually registered ahead of time.