Open Bug 1667807 Opened 5 years ago Updated 2 years ago

Add Telemetry to measure how long JumpLists block the main thread in the wild

Categories

(Core :: Widget: Win32, task, P3)

Product:
Core
Component:
Widget: Win32
Type:
task

Tracking

()

Project Flags:
Performance Impact medium

People

(Reporter: mconley, Unassigned)

References

Details

(Keywords: perf:responsiveness)

We should try to instrument the JumpList code to see how much they're impacting responsiveness. BHR data suggests there's impact out in the wild on Nightly - we should see how it is in the wider release population.

It would also be interesting to instrument usage of the feature, to see if it's being actually used, or if it's used so rarely that we could remove it instead of fixing it.

Whiteboard: [fxperf] → [fxperf:p2]

(In reply to Florian Quèze [:florian] from comment #1)

It would also be interesting to instrument usage of the feature, to see if it's being actually used, or if it's used so rarely that we could remove it instead of fixing it.

Jump Lists are pretty much table stakes for a first-class Windows application.

Severity: -- → S3
Priority: -- → P3
Performance Impact: --- → P2
Keywords: perf:responsiveness
Whiteboard: [fxperf:p2]
No longer blocks: 1529276
Depends on: 1529276
You need to log in before you can comment on or make changes to this bug.