Closed Bug 1265880 Opened 8 years ago Closed 8 years ago

Adjust velocity bias to see if checkerboarding improves

Categories

(Core :: Panning and Zooming, defect)

48 Branch
defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla49
Tracking Status
firefox47 --- wontfix
firefox48 --- fixed
firefox49 --- fixed

People

(Reporter: kats, Assigned: kats)

References

(Blocks 1 open bug)

Details

(Keywords: perf, Whiteboard: [gfx-noted])

Attachments

(1 file)

The apz.velocity_bias pref controls how much the displayport request is offset from the current scroll position based on the user's scroll velocity. It seems like in some cases this is too much; we should adjust this value to see how it impacts checkerboarding in the wild (using the telemetry probes for checkerboarding).
Attachment #8752869 - Flags: review?(mstange) → review+
Comment on attachment 8752869 [details]
MozReview Request: Bug 1265880 - Drop the APZ velocity bias to 0 on desktop. r?mstange

https://reviewboard.mozilla.org/r/52838/#review49724
I tried to post this comment earlier but apparently failed to:

The telemetry experiment is still too heavyweight for my liking and it doesn't look like the people with the power to change it have any interest in doing so. I'm just going to flip the pref to 0 on desktop and keep an eye on the regular telemetry dashboard to see if there's an impact. If the telemetry experiment process improves later we can still do an experiment to see what value is best.
Assignee: nobody → bugmail.mozilla
https://hg.mozilla.org/mozilla-central/rev/83e8b01535bf
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla49
For the record, Botond looked at the telemetry stats around this change and observed that the checkerboarding duration went up slightly when this landed. We also noticed that the checkerboarding peak went down slightly, and the checkerboarding severity metric remained roughly the same. The interpretation is that we made checkerboards longer but take up less of the screen.

Botond theorized that this was because we now have a few pixels of checkerboarding consistently while scrolling, because we are closer to the edge of the displayport. Whereas before we would have shorter but larger areas checkerboarded, in those cases where the velocity bias prediction was wrong.

We agreed that the new situation is probably better than the old situation, since it's more consistent and likely less noticeable to the user. However I suspect that maybe a small amount of velocity bias might be even better. We should probably still run an experiment with a few different values (0.25, 0.5, 0.75) to see what we get. However it's pretty low priority and we have other fish to fry.
Comment on attachment 8752869 [details]
MozReview Request: Bug 1265880 - Drop the APZ velocity bias to 0 on desktop. r?mstange

Approval Request Comment
[Feature/regressing bug #]: APZ
[User impact if declined]: Slightly worse checkerboarding in some conditions
[Describe test coverage new/current, TreeHerder]: No test coverage, but we have telemetry data on how this impacts the user experience. It seems to indicate a small positive effect
[Risks and why]: very low risk, just a pref modification that has been baking for a month
[String/UUID change made/needed]: none
Attachment #8752869 - Flags: approval-mozilla-beta?
Comment on attachment 8752869 [details]
MozReview Request: Bug 1265880 - Drop the APZ velocity bias to 0 on desktop. r?mstange

Improve the product, early in the cycle, taking it.
Should be in 48 beta 3
Attachment #8752869 - Flags: approval-mozilla-beta? → approval-mozilla-beta+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: