DEV/flutter_flutter
1
0
Fork 0
mirror of https://github.com/flutter/flutter.git synced 2026-02-20 02:29:02 +08:00
Code Issues Packages Projects Releases Wiki Activity
flutter_flutter/dev/benchmarks/microbenchmarks
History
Zachary Anderson 5188df0821
Revert gradle roll (#91459) 
* Revert "Mark last failing test after gradle update as flaky. (#91423)"

This reverts commit 46a52d03bddc74a78135d39ef2084503cc2156d7.

* Revert "fix android template for Gradle 7 (#91411)"

This reverts commit 51d06d537fe37dd8f42002346d8545a489aed427.

* Revert "Add explicit version for mac and windows openjdk. (#91408)"

This reverts commit bf429f2771f486602579bd5ff85ee2cfbb0794af.

* Revert "Update the openjdk version used by linux android tests. (#91405)"

This reverts commit 2144ab8b45b8da12a94838b092c8ebc62085457f.

* Revert "Migrate to Gradle 7.0.2 / AGP 7.0.1 (#90642)"

This reverts commit b6459f9b633279f84a92eabc6bc5f82304fc1eae.
2021-10-07 19:42:24 -07:00
..
android
Revert gradle roll (#91459)
2021-10-07 19:42:24 -07:00
ios
Migrate iOS project to Xcode 13 compatibility (#90304)
2021-09-22 13:23:05 -07:00
lib
Add a microbenchmark that measures performance of flutter compute. (#91257)
2021-10-04 14:16:23 -07:00
pubspec.yaml
Clean up dependency pins and update all packages (#91109)
2021-10-04 10:28:03 -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.