Page MenuHomePhabricator

Reduce the frequency of DOM scans to rebuild inlines when scrolling revisions

Authored by epriestley on Fri, May 15, 4:35 PM.



Ref T13513. See PHI1734, which raises a concern about the performance of large revisions near the 100-change threshold.

Currently, getInlines() is called whenever the scroll position transitions between two changesets, and it performs a relatively complicated DOM scan to lift inlines out of the document.

This shows up as taking a small but nontrivial amount of time in Firefox profiles and should be safely memoizable.

Test Plan
  • Under Firefox profiling, scrolled through a large revision.
  • Before change: getInlines() appeared as the highest-cost thing we're explicitly doing on profiles.
  • After change: getInlines() was no longer meaningfully represented on profiles.
  • Created inlines, edited inlines, etc. Didn't identify any broken behavior.

Diff Detail

rP Phabricator
Automatic diff as part of commit; lint not applicable.
Automatic diff as part of commit; unit tests not applicable.

Event Timeline

epriestley created this revision.Fri, May 15, 4:35 PM
This revision was not accepted when it landed; it landed in state Needs Review.Fri, May 15, 4:36 PM
epriestley requested review of this revision.
This revision was automatically updated to reflect the committed changes.