Closed Bug 879121 Opened 11 years ago Closed 11 months ago

Implement layer heat map based on the new layer diagnostics framework

Categories

(Core :: Graphics: Layers, defect)

Product:
Core
Component:
Graphics: Layers
Type:
defect

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: kanru, Unassigned)

References

Details

Draw layer heat map so that we could find layer overdraw easily.
Do we care about renderable things(such as image layer), or all geometry object(such as div)?

Renderable objects impact GPU, since overdraw may cause
1. memory throughput bound - too many sample fetch.
2. Pixel shader bound - too many pixels in a rendering round.

Geometry objects impact CPU, since we do all geometry caculation in CPU side.
I think we could render them in different color set.
OK.

Heat map is one way to measure pixel overdraw, I think it can help HTML5 application owner fix potential performance issue. 

Some more suggestions
1. Detect null draw: such as drawing a totally transparent layer.
2. Detect layers which are visible but be totally covered by other layer.
Severity: normal → S3

No longer applicable

Status: NEW → RESOLVED
Closed: 11 months ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.