flutter/dev/benchmarks/complex_layout
Jonah Williams 295eeaf100
[devicelab] retain first frame data in certain integration tests. (#143419)
Part of https://github.com/flutter/flutter/issues/143404

We currently drop the first N frames of all benchmarks. For the app based benchmarks (not microbenchmarks) this is harmful as we miss first time initialization costs in our CI.

Still need to do this with flutter/gallery, but that lives in a different repo.
2024-02-14 03:58:58 +00:00
..
android Reland "Update gradle lockfiles template (#140115)" (#143081) 2024-02-08 16:22:15 +00:00
ios Sort Swift imports in templates (#141487) 2024-01-16 18:07:21 +00:00
lib Remove "note that" in our documentation (as per style guide) (#120842) 2023-02-17 22:27:33 +00:00
macos Migrate Xcode projects last version checks to Xcode 15.1 (#140256) 2024-01-03 23:05:46 +00:00
test Implement switch expressions in dev/ (#139048) 2023-11-28 23:40:28 +00:00
test_driver [devicelab] retain first frame data in certain integration tests. (#143419) 2024-02-14 03:58:58 +00:00
test_memory Add bad scroller benchmark (#110362) 2022-08-26 18:50:07 +00:00
windows [Windows] Fix signed/unsigned int comparison (#142341) 2024-02-07 00:09:57 +00:00
pubspec.yaml Upgrade leak_tracker. (#143236) 2024-02-09 14:41:22 -08:00
README.md ✒ Spell Check All .md Files Related to Flutter 💙 (#61564) 2020-07-22 18:23:47 -07:00

complex_layout

Scrolling benchmark

To run the scrolling benchmark on a device:

flutter drive --profile test_driver/scroll_perf.dart

Results should be in the file build/complex_layout_scroll_perf.timeline_summary.json.

More detailed logs should be in build/complex_layout_scroll_perf.timeline.json.

Startup benchmark

To measure startup time on a device:

flutter run --profile --trace-startup

The results should be in the logs.

Additional results should be in the file build/start_up_info.json.