flutter/dev/benchmarks/complex_layout
Pierrick Bouvier 792e26df95
[Windows] Add target architecture to build path (#131843)
To implement windows-arm64 support, it is needed to add architecture as a subdirectory (https://github.com/flutter/flutter/issues/129805).

In short, when performing a flutter windows build, we have:
- Before: build/windows/runner/Release/gallery.exe
- After: build/windows/x64/runner/Release/gallery.exe

This convention follows what flutter linux build does.

Addresses: https://github.com/flutter/flutter/issues/129805
Addresses: https://github.com/flutter/flutter/issues/116196

Design doc: [flutter.dev/go/windows-arm64](https://flutter.dev/go/windows-arm64)
2023-08-31 09:09:02 -07:00
..
android Revert "[integration_test] upgrade androidx test to 1.4.0" (#124644) 2023-04-11 18:54:59 -07:00
ios iOS info.plist template: make UIViewControllerBasedStatusBar to be true (#128970) 2023-06-20 18:11:18 +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 14.3 (#125827) 2023-05-02 00:06:33 +00:00
test Add spaces after flow control statements (#126320) 2023-05-15 11:07:30 +02:00
test_driver Remove unnecessary null checks in dev/benchmarks (#118840) 2023-01-20 04:04:11 +00:00
test_memory Add bad scroller benchmark (#110362) 2022-08-26 18:50:07 +00:00
windows [Windows] Add target architecture to build path (#131843) 2023-08-31 09:09:02 -07:00
pubspec.yaml Update flutter packages to pick up latest vm_service (#133335) 2023-08-25 11:03:35 -07: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.