mirror of
https://github.com/flutter/flutter.git
synced 2025-06-03 00:51:18 +00:00
![]() If the benchmark runs out of time before it closes the drawer it is animating, it tries to divide by zero when computing the time per frame. Don't report time per frame for activities with zero frames. This likely only happens for the close frame action, but guards are added to all time per frame computations in this benchmark. |
||
---|---|---|
.. | ||
android | ||
ios | ||
lib | ||
money_asset_manifest.json | ||
pubspec.yaml | ||
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.