Confirmed users, Bureaucrats and Sysops emeriti
2,974
edits
Firefox/Features/Expose Add-on Performance: Difference between revisions
Jump to navigation
Jump to search
m
Firefox/Features/Expose Add-on Performance (view source)
Revision as of 03:42, 26 January 2012
, 26 January 2012no edit summary
No edit summary |
mNo edit summary |
||
| Line 1: | Line 1: | ||
{{FeatureStatus | {{FeatureStatus | ||
|Feature name=Expose add-on performance information in Firefox | |Feature name=Expose add-on performance information in Firefox | ||
|Feature stage= | |Feature stage=On hold | ||
|Feature status=In progress | |Feature status=In progress | ||
|Feature health=OK | |Feature health=OK | ||
| Line 7: | Line 7: | ||
}} | }} | ||
{{FeatureTeam | {{FeatureTeam | ||
|Feature product manager=Justin Scott | |Feature product manager=Justin Scott & Asa Dotzler | ||
|Feature feature manager=Justin Scott | |Feature feature manager=Justin Scott | ||
|Feature lead engineer=Hernan Rodriguez Colmeiro, Dave Dash | |Feature lead engineer=Hernan Rodriguez Colmeiro, Dave Dash, Justin Dolske | ||
|Feature privacy lead=Sid Stamm | |Feature privacy lead=Sid Stamm | ||
|Feature qa lead=Henrik Skupin | |Feature qa lead=Henrik Skupin | ||
| Line 15: | Line 15: | ||
}} | }} | ||
{{FeaturePageBody | {{FeaturePageBody | ||
|Feature overview=Users should be informed when an add-on they have installed | |Feature overview=Users should be informed when an add-on they are about to install or have installed causes Firefox performance and or memory problems. This information should be presented at AMO and in the Firefox Add-ons Manager. | ||
|Feature users and use cases=We should develop a new Add-ons policy, and acompanying AMO and Firefox technology, which says that we will inform our add-on users and prospective add-on users about specific add-ons that can be proved to have a significant and excessive impact on memory usage and/or performance. I propose we test for start-up performance impact, page load performance impact, start-up memory use impact, and memory leaks. | |||
The policy should specify that we will notify the authors of add-ons as soon as we discover a problem and it should have a grace period for correcting any excessive memory or performance impact. I propose, as a straw-man, half a release cycle or 3 weeks from notification. | |||
If after the grace period the add-on is not brought within compliance, we should add it to a list of ill-behaving add-ons. That list would be consumed by both AMO and the Firefox client. Both apps would use the list to display warnings to users about the impact of the add-on. | |||
If after an additional 3 weeks of the add-on being flagged publicly, (again, a straw man) it is not corrected, we should escalate the content of and the and visibility of the warning message. | |||
At AMO, I believe these poorly-performing add-ons should be flagged at the add-on install page. The warning should be firm but friendly -- something like "Mozilla testing has determined that this add-on may cause Firefox performance problems". If, after some period if time from the public warning the add-on is not corrected, the message should be escalated to display in search results and with a text that would more seriously deter users, something like "This add-on is known to cause serious Firefox issues. Use at your own Risk". | |||
In the Firefox client, the flagged add-ons should display warning text in the Add-ons Manager (where informed users, or users following the instructions of a support article or other help, would see it,) and for the escalation period, to an infobar. | |||
This would give add-on authors 3 weeks to fix problems before potential users and some of the installed base are notified, and another 3 weeks before most potential and all existing users would see the more dire warning. | |||
|Feature dependencies=Add-on testing capabilities, manual or automated. | |||
An AMO API for "warned add-ons" and for "doubly warned add-ons" | |||
AMO and Firefox code to access this API, get the lists, and display UI based on the lists. | |||
|Feature ux design=* [https://people.mozilla.com/~jboriss/dump/olds_em_mocks_with_performance/as_a_percentage.png Early design mockup]: shows percentage of runtime used for each addon. | |Feature ux design=* [https://people.mozilla.com/~jboriss/dump/olds_em_mocks_with_performance/as_a_percentage.png Early design mockup]: shows percentage of runtime used for each addon. | ||
* [https://bugzilla.mozilla.org/attachment.cgi?id=535788]: newer mockup of the first stage | * [https://bugzilla.mozilla.org/attachment.cgi?id=535788]: newer mockup of the first stage | ||
| Line 37: | Line 53: | ||
}} | }} | ||
{{FeatureTeamStatus | {{FeatureTeamStatus | ||
|Feature products notes=For more information, please see [http://blog.mozilla.com/addons/2011/04/01/improving-add-on-performance/] [http://blog.mozilla.com/addons/2011/04/12/update-on-add-on-performance-testing/] [http://alice.nodelman.net/blog/post/addon-performance-testing-updates-and-future-work/] | |||
|Feature security status=sec-review-complete | |Feature security status=sec-review-complete | ||
|Feature security health=OK | |Feature security health=OK | ||