flutter/dev/benchmarks/complex_layout
auto-submit[bot] 778eaf6c1d
Reverts "Manual engine roll to 6884e83 (#150733)" (#150746)
Reverts: flutter/flutter#150733
Initiated by: gmackall
Reason for reverting: This breaks apps that use plugins that use `compileSdk` 31, some of which we use in our postsubmit (so it blocks the tree). 
Original PR Author: gmackall

Reviewed By: {jason-simmons}

This change reverts the following previous change:
Manual engine roll to https://github.com/flutter/engine/pull/53532, because the roll requires lockfile generation.
2024-06-25 01:20:29 +00:00
..
android Reverts "Manual engine roll to 6884e83 (#150733)" (#150746) 2024-06-25 01:20:29 +00:00
ios [iOS] Migrate @UIApplicationMain attribute to @main (#146707) 2024-04-16 22:13:03 +00:00
lib Remove "note that" in our documentation (as per style guide) (#120842) 2023-02-17 22:27:33 +00:00
macos [macOS] Migrate @NSApplicationMain attribute to @main (#146848) 2024-04-18 03:08:36 +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 Fix flaky complex_layout_scroll_perf__memory & flutter_gallery__memory_nav (#150368) 2024-06-17 17:14:47 +00:00
windows [Windows] Drop support for Windows 7/8 apps in template (#146668) 2024-04-12 01:07:20 +00:00
pubspec.yaml Remove discontinued device_info and connectivity plugins from flutter_gallery, roll pub packages (#150585) 2024-06-21 23:10:24 +00:00
README.md Added missing code block language in docs (#147481) 2024-05-01 14:44:27 +00: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.