History

* Run update-packages

* Update DwdsLauncher, disable failing test

* Fix analyze error

Co-authored-by: Jenn Magder <magder@google.com>

2022-04-07 17:07:05 -07:00

android

Reland "Exit on deprecated v1 embedding when trying to run or build" (#92901 ) (#93566 )

2021-11-12 15:52:32 -08:00

ios

Run CADisableMinimumFrameDurationOnPhone migration on all example apps (#101314 )

2022-04-05 15:38:06 -07:00

lib

Added the ability for microbenchmarks to print the probability of the result. (#101154 )

2022-04-06 09:41:11 -07:00

pubspec.yaml

Run update-packages (#101450 )

2022-04-07 17:07:05 -07:00

README.md

Restore the original name of the velocity tracker microbenchmark (#64060 )

2020-08-19 00:41:06 -07:00

README.md

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.