1271769 - Add a telemetry probe for measuring the time spent waiting in queue for keyboard/mouse events.

Status: RESOLVED WORKSFORME

(Core :: JavaScript Engine, defect)

Description

[Morgan Phillips [:mrrrgn]]

11:51 AM <bz> jorendorff: Right now the event loop just has a bunch of nsIRunnable*
11:51 AM <bz> jorendorff: How is it supposed to prioritize between them?
11:51 AM <•jorendorff> ...great
11:52 AM <•jorendorff> bz: i don't suppose that QIs to anything interesting...
11:52 AM <sfink> give nsIRunnable a priority field and use a priority queue instead of a list?
11:53 AM <•jorendorff> we can figure out what it would take to have relevant information, i imagine *waves hands*
11:53 AM <sfink> or more likely, a fixed array of 3 priorities
11:54 AM <•jorendorff> bz: To take a step back, where do you think this ranks in terms of reasons the Firefox UI becomes unresponsive (for noticeable amounts of time)
12:01 PM <sfink> do we have any telemetry on that question? It's sort of like how long an event waits in the event queue, but maybe conditioned on a priorityish thing that we probably don't have yet
12:01 PM <sfink> that question == how common is priority inversion a problem for real-world responsiveness, I mean
12:01 PM <•jorendorff> very interesting thing to measure
12:02 PM <sfink> maybe just do it for mouse/key handling or something
12:02 PM <•jorendorff> yeah

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The bug assignee didn't login in Bugzilla in the last 7 months, so the assignee is being reset.

Comment 2

[Matthew Gaudet (he/him) [:mgaudet]]

See input_event_queued_click_ms and input_event_queued_keyboard_ms

https://glam.telemetry.mozilla.org/firefox/probe/input_event_queued_click_ms/explore?currentPage=1