Scrolling perf regression in Complex Layout benchmark

[yjbanov]

The complex layout benchmark seems to show a performance regression in the Tabs API change. It is mostly visible in worst frame build times and missed rasterizer (GPU) frame counts.

Steps to Reproduce

cd dev/devicelab
dart bin/run.dart -t bin/tasks/complex_layout_scroll_perf__timeline_summary.dart

Logs

[Hixie]

@HansMuller Looking at this, my first step towards debugging it would be to run the benchmarks under the profiler immediately before the suspect patch and immediately after the suspect patch to see what the difference is.

[HansMuller]

I was able to confirm the problem and that it was introduced by #7387. Since then the benchmark's performance has returned to normal.

It would be useful to sort out what caused the regression however at the moment #7763 makes it difficult to profile the benchmark.

[Hixie]

@HansMuller #7763 is obsolete now, so this should be testable again.

[yjbanov]

This has improved greatly since the issue was filed. Closing.

[github-actions]

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 -v and a minimal reproduction of the issue.