-
Notifications
You must be signed in to change notification settings - Fork 30.1k
Closed
Labels
c: contributor-productivityTeam-specific productivity, code health, technical debt.Team-specific productivity, code health, technical debt.c: performanceRelates to speed or footprint issues (see "perf:" labels)Relates to speed or footprint issues (see "perf:" labels)engineflutter/engine related. See also e: labels.flutter/engine related. See also e: labels.
Description
Considering that performance overlay is one of our main performance tools, we should:
- Benchmark performance overlay in our device lab. Currently all our performance tests don't have performance overlay enabled.
- Improve its performance to be less than 1ms per frame. Currently, it's about 4-6ms per frame on Moto G4. That time doesn't even include the actual GPU rendering time. It's just Skia doing CPU work before sending it to GPU... 4-6ms looks quite unacceptable as the whole frame's budget is only 16ms. We should be able to achieve a big speedup by caching the performance overlay to an offscreen buffer. For each new frame, we just add a new vertical blue segment.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
c: contributor-productivityTeam-specific productivity, code health, technical debt.Team-specific productivity, code health, technical debt.c: performanceRelates to speed or footprint issues (see "perf:" labels)Relates to speed or footprint issues (see "perf:" labels)engineflutter/engine related. See also e: labels.flutter/engine related. See also e: labels.
