Closed Bug 1365334 Opened 7 years ago Closed 7 years ago

Parent INPUT_EVENT_RESPONSE_MS p95 regressed from 18.3 to 20.7ms on 2017-05-06 build

Categories

(Core :: General, defect)

Product:
Core
Component:
General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INCOMPLETE
Project Flags:
Performance Impact high

People

(Reporter: ehsan.akhgari, Unassigned)

References

Details

Telemetry: https://mzl.la/2rcR8Nd
It would be nice to find someone to take care of this who isn't me. :-)
Flags: needinfo?(nihsanullah)
This regression is even more visible in the INPUT_EVENT_RESPONSE_COALESCED_MS probe: https://mzl.la/2qxhjx6, from 32.85ms to 38.14ms.
See Also: → 1366156
The INPUT_EVENT_QUEUED_APZ_MOUSE_MOVE_MS and INPUT_EVENT_QUEUED_APZ_WHEEL_MS probe also shows clear regression around 4/5 and 5/6 so I think we can narrow down the regression to APZ events.

Telemetry: https://mzl.la/2q89QWA https://mzl.la/2q8rPMI
(In reply to Kan-Ru Chen [:kanru] (UTC+8) from comment #4)
> The INPUT_EVENT_QUEUED_APZ_MOUSE_MOVE_MS and INPUT_EVENT_QUEUED_APZ_WHEEL_MS
> probe also shows clear regression around 4/5 and 5/6 so I think we can
> narrow down the regression to APZ events.
> 
> Telemetry: https://mzl.la/2q89QWA https://mzl.la/2q8rPMI

Actually that only means the events are in the queue longer since wheel and mousemoe events are fired frequently.
Backed out bug 1352889 today to see whether it is the cause.
[ni=kanru to investigate whether comment 6 helped]
Flags: needinfo?(kchen)
The backout of bug 1352889 didn't make any difference.  I'm going to reland it, but that means you need to look for a different culprit here.
See bug 1362094 comment 25. We decided this bug is INCOMPLETE due to the limitation of the probes.
Status: NEW → RESOLVED
Closed: 7 years ago
Flags: needinfo?(nihsanullah)
Flags: needinfo?(kchen)
Resolution: --- → INCOMPLETE
Performance Impact: --- → P1
Whiteboard: [qf:p1]
You need to log in before you can comment on or make changes to this bug.