flutter/dev/benchmarks/microbenchmarks
Jonah Williams 04f7c9d52e
[flutter_tools] update dwds, roll to null-safe file and process (#64195)
Update to latest dwds, file-nullsafety, and process-nullsafety for #62886
2020-08-19 16:59:52 -07:00
..
android move compile/target sdk versions to 29 (#62799) (#63008) 2020-08-11 14:51:02 -07:00
ios Move embedding and linking Flutter frameworks into the tool (#51453) 2020-03-03 12:11:28 -08:00
lib Restore the original name of the velocity tracker microbenchmark (#64060) 2020-08-19 00:41:06 -07:00
pubspec.yaml [flutter_tools] update dwds, roll to null-safe file and process (#64195) 2020-08-19 16:59:52 -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.