Firefox:FrontEndPerformance: Difference between revisions
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
=Requirements= | =Requirements= | ||
We need an end-to-end approach to front-end performance, from detection to reporting to resolution to regression-catching. | |||
Detection and Reporting: | |||
* A new keyword for ui-responsiveness bugs? | |||
* Extension for reporting beachballing, script hangs? | |||
Framework: | |||
We need a framework for front-end performance testing, that provides reliable measurements of the performance of UI actions. | We need a framework for front-end performance testing, that provides reliable measurements of the performance of UI actions. | ||
Revision as of 21:50, 13 January 2009
Requirements
We need an end-to-end approach to front-end performance, from detection to reporting to resolution to regression-catching.
Detection and Reporting:
- A new keyword for ui-responsiveness bugs?
- Extension for reporting beachballing, script hangs?
Framework: We need a framework for front-end performance testing, that provides reliable measurements of the performance of UI actions.
- integrates with Talos
- tests need to run in full browser instance *or* in xpcshell
- reports to Tinderbox
- reports to graph server
- need to graph individual test scores over time
- New Graph Server (work on hold until this is done)
Proposal
Timeline
Meeting Notes
Action Items
| item | owner | bugs | status |
| find spectator owner, ask about status, and MoCo rollout | dietrich | ken kovash says they have a Q4 goal for a web front-end to view this data, so news in the next couple of weeks. | |
| design basic high-stress profiles | UNOWNED | ||
| re-enable daily shark builds | build | bug 448727 | Not happening in 2008 (see bug) |
| file bug for removing extension manager code for migrating old profiles | mossop | Complete | |
| fix dtrace js probes on trunk | sayrer | ||
| get a startup timeline | cbartley | bug 467953 | talk to mobile & Taras work they've done on it |