flutter/dev/benchmarks/microbenchmarks
2022-12-14 13:13:05 -08:00
..
android [Android] Bump Kotlin and Android Gradle plugin versions in tests (#112728) 2022-10-07 12:30:27 +00:00
ios Set Xcode build script phases to always run (#108331) 2022-07-26 19:20:07 +00:00
lib Revert "Speed up first asset load by encoding asset manifest in binary rather than JSON (#113637)" (#116662) 2022-12-07 17:29:05 +00:00
money_asset_manifest.json Add asset manifest parsing benchmark (#112836) 2022-10-07 13:39:35 +00:00
pubspec.yaml Upgrade dependencies (#117007) 2022-12-14 13:13:05 -08: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.