development/flutter
development/flutter
1
0
Fork 0
mirror of https://github.com/flutter/flutter synced 2024-10-14 04:02:56 +00:00
Code Issues Packages Projects Releases Wiki Activity
flutter/dev/benchmarks/microbenchmarks
History
Jenn Magder d7e49e559b
Run update packages, pick up file 6.1.1 (#82770)
2021-05-18 13:09:03 -07:00
..
android migrate from jcenter to mavencentral (#80908) 2021-04-21 21:41:07 -07:00
ios Build iOS apps using Swift Packages (#73508) 2021-01-07 15:59:09 -08:00
lib Wait for frame rendering to stabilize before running the all_elements_bench benchmark (#81086) 2021-04-23 20:29:03 -07:00
pubspec.yaml Run update packages, pick up file 6.1.1 (#82770) 2021-05-18 13:09: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.