Closed Bug 1583841 Opened 4 months ago Closed 3 months ago

Smart profiler HUD

Categories

(Core :: Graphics: WebRender, task, P3)

task

Tracking

()

RESOLVED FIXED

People

(Reporter: nical, Assigned: nical)

References

(Blocks 2 open bugs)

Details

Attachments

(7 files)

The builtin webrender profiler HUD is too large to display at all times. The compact profiler is useful but it doesn't always have the relevant information.

I would like to have a profiler that only shows information when the value is higher than a certain value. For example only show the number of draw calls if it is greater than 80, only show the number of alpha targets if it is greater than 2, etc.
If a field is displayed, keep it for a second to avoid blinking.

Pushed by nsilva@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/8aeb2407e5e5
Add a smart profiler HUD. r=jrmuizel
https://hg.mozilla.org/integration/autoland/rev/9b5653a5fae4
Define some expected ranges for webrender's smart profiler. r=gw

When we are not scrolling or animating it can be normal for there to be a long pause between frames, in which case highlighting the FPS counter in the profiler is distracting.

Depends on D49619

Assignee: nobody → nical.bugzilla
Keywords: leave-open
Pushed by nsilva@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/5979a2132006
Add an expected range in ResourceProfileCounter. r=gw
https://hg.mozilla.org/integration/autoland/rev/8cc42e92e6ef
Include some ResourceProfileCounters in the smart profiler. r=gw
https://hg.mozilla.org/integration/autoland/rev/16bed925e3ac
Highlight values in red in the full and compact profilers when values are outside their expected range. r=gw
https://hg.mozilla.org/integration/autoland/rev/1ad5346d3fa4
Don't set an expected range for the FPS counter. r=gw
Pushed by nsilva@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/06e6c1909fe1
Adjust expected gpu cache blocks constants. r=kvark
Status: NEW → RESOLVED
Closed: 3 months ago
Keywords: leave-open
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.