Performance/Snappy/2011-12-01: Difference between revisions

Performance/Snappy/2011-12-01 (view source)

Revision as of 23:30, 1 December 2011

101 bytes added , 1 December 2011

→‎Roundtable

Tglek

Confirmed users

381

edits

@@ Line 7: / Line 7: @@
 * file bugs for product P1 responsiveness issues - lmandel
-==Roundtable==
+==Notes==
+* chromehang bugs should probably be [Snappy]
-* (dmandelin) What kinds of comparisons can we do with Telemetry, and how easily?
+** helped prioritize known problems, uncovered new ones
-** Example: Can we see the effect of landing a change?
+** Evidence that sqlite is not our #1 problem
-** Example 2: Can we do A/B testing?
+** only caught the first lag
-* (dmandelin) Closing a tab is frequently not snappy for me. What's the easiest way to diagnose this?
+Will start by integrating in a non crash way with Telemetry - can look at a UI to allow the user to kill the browser afterwards
-* (Asa) I'd like to propose that we instrument and get timing data for each of the starred items starting [https://etherpad.mozilla.org/desktop-responsiveness at line 49 here]  These are what I consider the top primary UI features. The un-starred items are next.
+Filed https://bugzilla.mozilla.org/show_bug.cgi?id=706916 needs telemetry-privacy review.
-* (Asa) A proposal for snappy:Priority criteria: If it's primary UI, it's a priority until it's snappy. If it's secondary UI, it's only a priority if it's horrible. So, for example, performance of the Awesomebar pop-up is a priority, even if it feels OK -- it needs to be "instant". Performance of tabs the Add-ons manager is secondary UI and it's "good enough" right now so not a priority. However, performance of deleting history items, also secondary UI, is so catastrophically bad that it should be a priority.
+One-off hogs that can run for multiple seconds of minutes:
+* cache bug https://bugzilla.mozilla.org/show_bug.cgi?id=705761
+  cache bug https://bugzilla.mozilla.org/show_bug.cgi?id=701909
+* fonts 705287 705258 705594
+will meet about cache bugs separately
+* sqlite 704933 699051
+"Small" Jank:
+* we need a way to track when we should be painting at a certain rate and aren't. The refresh driver should help here. It will tell us when we're try to paint.
+* Measure animation lag for throbber, progress bars, etc
+Jeff will create/add bugs about animation https://bugzilla.mozilla.org/show_bug.cgi?id=706919
+* Asa has a list of UI jank to track
+https://etherpad.mozilla.org/desktop-responsiveness - see starred items after line 49
+- lawrence will file bugs for top issues