Repository navigation
[Impeller] All framework devicelab benchmarks are skipping the first (several) frames. #143404
Description
As a result, we're not directly measuring the potential performance improvement from changes such as flutter-team-archive/engine#50521 . From doing some research, this was done intentionally - speciifcally to ignore the warm up frames / shader work done in 2019.
Even if this logic was removed, because the test runner is responsible for connecting to the application and enabling the timeline range, the first frame might not be present and/or this could be flaky.
We may need an alternative test harness to capture first frame times.
Activity
jonahwilliams commentedon Feb 13, 2024
Example: local run --enable-impeller --profile, looking at Dart timeline:
driver test, with await first frame commented out:
jonahwilliams commentedon Feb 13, 2024
It looks like we only indirectly capture this using
flutter/packages/flutter_tools/lib/src/tracing.dart
Line 196 in 5025681
We have timeToFirstFrameRasterizedMicros, but no actual measurement of frame time.
timeToFirstFrameRasterizedMicros
timeToFirstFrameRasterizedMicros
jonahwilliams commentedon Feb 13, 2024
This is a framework generated event.
[devicelab] retain first frame data in certain integration tests. (#1…
[devicelab] retain prior events for flutter gallery. (#143554)
github-actions commentedon Mar 1, 2024
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.