-
Notifications
You must be signed in to change notification settings - Fork 28.9k
Closed
Labels
P1High-priority issues at the top of the work listHigh-priority issues at the top of the work listc: performanceRelates to speed or footprint issues (see "perf:" labels)Relates to speed or footprint issues (see "perf:" labels)c: regressionIt was better in the past than it is nowIt was better in the past than it is nowengineflutter/engine repository. See also e: labels.flutter/engine repository. See also e: labels.perf: speedPerformance issues related to (mostly rendering) speedPerformance issues related to (mostly rendering) speedteam: benchmarkPerformance issues found by inspecting benchmarksPerformance issues found by inspecting benchmarks
Milestone
Description
I've missed this one for the last few days, because it's drifted in and out of being red. It's pretty clear now looking at the history that it's regressed slightly:
It's difficult for me to pinpoint a single roll causing it. The first time it went red was in restoring it after a gap (#60415), but I don't think that's it; I rather prefer engine roll #60384, in which the benchmark was still green, but a jump from its predecessor.
I'm tentatively giving this to the engine team, and given that it's not a huge regression, assigning it a P2 for investigation.
Metadata
Metadata
Assignees
Labels
P1High-priority issues at the top of the work listHigh-priority issues at the top of the work listc: performanceRelates to speed or footprint issues (see "perf:" labels)Relates to speed or footprint issues (see "perf:" labels)c: regressionIt was better in the past than it is nowIt was better in the past than it is nowengineflutter/engine repository. See also e: labels.flutter/engine repository. See also e: labels.perf: speedPerformance issues related to (mostly rendering) speedPerformance issues related to (mostly rendering) speedteam: benchmarkPerformance issues found by inspecting benchmarksPerformance issues found by inspecting benchmarks