History

Alexander Aprelev 98120d19d3

Add a microbenchmark that measures performance of flutter compute. (#91257 )

* Add a microbenchmark that measures performance of flutter compute.

This benchmark should show performance improvements when compute is switched to Isolate.exit

* Fix analyzer warnings, increase warmup iterations

* Fix license header

2021-10-04 14:16:23 -07:00

android

Change project.buildDir in standalone subprojects property (#91030 )

2021-10-01 17:18:05 -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.