History

[web] move e2e tests from flutter/engine to flutter/flutter (#86119 )

* [web] move e2e tests from flutter/engine to flutter/flutter
* flutter update-packages --force-upgrade

2021-07-09 15:31:49 -07:00

android

Add Gradle lockfiles and tool to generate them (#83067 )

2021-05-21 13:04:03 -07:00

ios

Migrate iOS app deployment target from 8.0 to 9.0 (#85174 )

2021-06-24 10:21:05 -07:00

lib

Prep for new directives_ordering (#84579 )

2021-06-14 12:13:28 -07:00

pubspec.yaml

[web] move e2e tests from flutter/engine to flutter/flutter (#86119 )

2021-07-09 15:31:49 -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.