Electrolysis/Release Criteria/Plugin Jank: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
m (reformat page)
(Updating with results of analysis.)
Line 12: Line 12:


== BLOCKED_ON_PLUGIN_INSTANCE_INIT_MS ==
== BLOCKED_ON_PLUGIN_INSTANCE_INIT_MS ==
== BLOCKED_ON_PLUGIN_INSTANCE_DESTROY_MS ==


This seems to be roughly the same between e10s and non-e10s.
There are no submissions for these histograms from clients with E10s enabled. For example: http://mzl.la/21HFP90
 
== BLOCKED_ON_PLUGIN_INSTANCE_DESTROY_MS ==


Also roughly the same, although perhaps a bit worse in e10s.
I wonder if this has to do with async plugin init...


= Bugs =
= Bugs =

Revision as of 17:22, 2 March 2016

Plugin jank is in the category "things that may regress up to 5% as a tradeoff for other benefits". Any regression in the *chrome* process should stop ship. Regressions in the content process are not nearly so important.

RASCI

  • Responsible: chutten
  • Accountable: bsmedberg
  • Supporting: aklotz
  • Consulted:
  • Informed: elan, cpeterson

Metrics

BLOCKED_ON_PLUGIN_INSTANCE_INIT_MS

BLOCKED_ON_PLUGIN_INSTANCE_DESTROY_MS

There are no submissions for these histograms from clients with E10s enabled. For example: http://mzl.la/21HFP90

I wonder if this has to do with async plugin init...

Bugs

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);

Retrieved from "https://wiki.allizom.org/index.php?title=Electrolysis/Release_Criteria/Plugin_Jank&oldid=1119580"