flutter/dev/benchmarks/microbenchmarks
2020-10-01 09:54:07 -07:00
..
android move compile/target sdk versions to 29 (#62799) (#63008) 2020-08-11 14:51:02 -07:00
ios Require xcode_backend.sh arguments (introduced in Flutter v0.0.7) (#65124) 2020-09-02 16:33:26 -07:00
lib Deprecate VelocityTracker default constructor and added VelocityTracker.withKind constructor (#66043) 2020-09-17 15:18:31 -07:00
pubspec.yaml update stack_trace dep (and others) (#67057) 2020-10-01 09:54:07 -07: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.