1663710 - Too many users have long wait times for printer information to be fetched

Status: RESOLVED FIXED

(Core :: Printing: Setup, defect, P2)

Description

[Jonathan Watt [:jwatt]]

Filing this as a placeholder bug. Our telemetry tells us that a large percentage of users on macOS and Linux wait 10 seconds or more for information about their printers to be fetched. That would seem to block running the Shirley expriment on macOS or Linux.

In the couple of days while the commit to gather this telemetry was in beta 81 before the pref auto-disabled in b7, on macOS each day about 15% (400) of the recorded prints required >10s to fetch the printer list. On Linux it was around 9% (46).

Comment 1

[Emily McDonough [:alaskanemily]]

jwatt: Is this different from bug 1661157?

Comment 2

[Jonathan Watt [:jwatt]]

(In reply to Emily McDonough [:alaskanemily] from comment #1)

jwatt: Is this different from bug 1661157?

This is specifically about monitoring the telemetry we're gathering to understand what our users as a whole are experiencing, it's not about a specific source of slowness. If the telemetry we gather shows the slowness is gone after bug 1661157 then great. (I guess we should be able to tell some time next week, although the data is sparse on Nightly.)

Comment 3

[Jonathan Watt [:jwatt]]

We decided that the wait times are not a blocker for the experiment in 82, unless we see the data change as the Beta telemetry comes in.

Comment 4

[Lee McFarland]

(In reply to Jonathan Watt [:jwatt] from comment #3)

We decided that the wait times are not a blocker for the experiment in 82, unless we see the data change as the Beta telemetry comes in.

Wait times could be perceived by some end users as unacceptable. If that does happen, such people could set the pref print.tab_modal.enabled to FALSE

Comment 5

[Jonathan Watt [:jwatt]]

(In reply to Lee McFarland from comment #4)

Wait times could be perceived by some end users as unacceptable. If that does happen, such people could set the pref print.tab_modal.enabled to FALSE

Yes, that could definitely happen, but this is an experiment (one week only, I think) for a small proportion of users. We'll continue working on performance until we get to the point when telemetry tells us that we can turn it on for everyone permanently.

For v82 there's nothing more we'll be landing, however. Moving this to v83 now to keep it on the radar.

Comment 6

[Sean Voisen (:svoisen)]

Downgrading this based on recent trends in telemetry.

Comment 7

[Jonathan Watt [:jwatt]]

Since we shipped this bug has served its purpose. Specific issues that are tracked by other bugs will remain open.