Closed Bug 1356406 Opened 8 years ago Closed 6 years ago

Run a Telemetry experiment to vet D3D11 double-buffering

Categories

(Core :: Graphics: Layers, enhancement, P3)

Product:
Core
Component:
Graphics: Layers
Version:
55 Branch
Platform:
Unspecified
Windows 10
Type:
enhancement

Tracking

()

Status:
RESOLVED WONTFIX
Tracking Flags:
Tracking Status
firefox55 --- affected

People

(Reporter: u279076, Assigned: u279076, NeedInfo)

References

Details

(Whiteboard: [gfx-noted])

This is bug tracks running a Telemetry Experiment to A/B test D3D11 double-buffering as implemented in bug 1352163.
Bas and Anthony, can you please let me know which Telemetry probes I should be tracking? I can track stability data easily enough but I'd like to know what I should be tracking in terms of performance. Thanks
Flags: needinfo?(bas)
Flags: needinfo?(ajones)
I'm having a hard time finding the right telemetry probes, I'll ask around some more but COMPOSITE_FRAME_ROUNDTRIP_TIME could be interesting I suppose?
Flags: needinfo?(bas)
Gerald, Anthony has yet to respond. Do you have any insight as to which probes I might track for this?
Flags: needinfo?(ajones) → needinfo?(gsquelart)
Sorry, forgot to reply here. Unfortunately, from the angle I'm familiar with (media playback, which is mostly about decoding) I don't see which probe could be affected by this change. It sounds more like a graphics-side improvement, so I'll nominate Matt as the next person-who-should-know-better!
Flags: needinfo?(gsquelart) → needinfo?(matt.woodrow)
Closing this as I am no longer on the GFX team, assuming this is no longer needed.
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.