flutter/dev/benchmarks/microbenchmarks
Greg Spencer 31e3364771
Update outdated runners in the benchmarks folder (#91126)
This change updates the platform runners in the benchmarks subdir.

I've attempted to replace the entire group with new code as if the project were recreated with flutter create so that they don't become a Frankenstein of minor changes to make it work again, but just plain old generated code that can be replaced and updated in place.
2021-10-19 08:27:29 -07:00
..
android Update outdated runners in the benchmarks folder (#91126) 2021-10-19 08:27:29 -07:00
ios Update outdated runners in the benchmarks folder (#91126) 2021-10-19 08:27:29 -07:00
lib Enable avoid_redundant_argument_values lint (#91409) (#91462) 2021-10-08 09:25:14 -07:00
linux Update outdated runners in the benchmarks folder (#91126) 2021-10-19 08:27:29 -07:00
macos Update outdated runners in the benchmarks folder (#91126) 2021-10-19 08:27:29 -07:00
web Update outdated runners in the benchmarks folder (#91126) 2021-10-19 08:27:29 -07:00
windows Update outdated runners in the benchmarks folder (#91126) 2021-10-19 08:27:29 -07:00
.metadata Update outdated runners in the benchmarks folder (#91126) 2021-10-19 08:27:29 -07:00
pubspec.yaml Run "flutter update-packages --force-upgrade" to get latest DDS (#91736) 2021-10-13 10:58:04 -07:00
README.md Restore the original name of the velocity tracker microbenchmark (#64060) 2020-08-19 00:41:06 -07:00

microbenchmarks

To run these benchmarks on a device, first run `flutter logs' in one window to see the device logs, then, in a different window, run any of these:

flutter run --release lib/gestures/velocity_tracker_bench.dart
flutter run --release lib/gestures/gesture_detector_bench.dart
flutter run --release lib/stocks/animation_bench.dart
flutter run --release lib/stocks/build_bench.dart
flutter run --release lib/stocks/layout_bench.dart

The results should be in the device logs.

Avoid changing names of the benchmarks

Each microbenchmark is identified by a name, for example, "catmullrom_transform_iteration". Changing the name of an existing microbenchmarks will effectively remove the old benchmark and create a new one, losing the historical data associated with the old benchmark in the process.