Paul Berry
d2df7ce24a
Now that https://dart-review.googlesource.com/c/sdk/+/291500 has landed, `dart run` now tries to invoke `dart pub` before execution. This doesn't work when running scripts inside the SDK, because the SDK doesn't use pub to get its dependencies. So scripts in the SDK now need to be run with `--no-pub`. Change-Id: Ic320b717b2d45278cd26d373ae0823c2935ce102 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/292720 Reviewed-by: Johnni Winther <johnniwinther@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 --no-pub <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.