Closed Bug 1532410 Opened 6 years ago Closed 5 years ago

Understand why fixing the Intel framebuffer read patch didn't move our metrics

Categories

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

Product:
Core
Component:
Graphics: WebRender
Type:
defect

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: jrmuizel, Assigned: jrmuizel)

References

(Blocks 1 open bug)

Details

The patch in bug 1528865 has a large impact on GPU performance on Intel but it didn't move our metrics really at all. Understanding why will be helpful.

Depends on: 1524090
Blocks: wr-67
Priority: -- → P2
Assignee: nobody → jmuizelaar

I tried and failed so far to find out what's going on here.

Blocks: wr-68
No longer blocks: wr-67
Priority: P2 → P3
Blocks: wr-intel
No longer blocks: wr-68

Which metric was this supposed to move? If CONTENT_FULL_FRAME_TIME then it might be because of bug 1544039.

Blocks: wr-intel-mvp
No longer blocks: wr-intel
No longer blocks: wr-intel-mvp
Blocks: wr-intel
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX

Not worth the effort at this point.

You need to log in before you can comment on or make changes to this bug.