Closed Bug 1542276 Opened 5 years ago Closed 28 days ago

Don't auto-normalize WR profiler graphs

Categories

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

Product:
Core
Component:
Graphics: WebRender
Type:
defect

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: kvark, Unassigned)

References

Details

When "gfx.webrender.debug.profiler" is enabled, we output 4 graphs:

  1. CPU backend
  2. CPU renderer
  3. DisplayList IPC
  4. GPU

These always get auto-normalized to the max value in the graph, which makes the whole graph jump back and forth in height scaling. It's not very convenient or useful to look at as it stands now.

Instead, we should establish fixed expectations/budget for each of those, such that that it's clear from a single look at the graph that we are below or above the expected times.

The priority flag is not set for this bug.
:jbonisteel, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(jbonisteel)
Blocks: stage-wr-next
Flags: needinfo?(jbonisteel)
Priority: -- → P3
Blocks: 1782834
Severity: minor → S4
Status: NEW → RESOLVED
Closed: 28 days ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.