Firefox:FrontEndPerformance

From MozillaWiki
Jump to navigation Jump to search

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.

Proposal

Research/Tracking

  • Implement about:me reporting (bug 480154)
  • Use [TSnappiness] whiteboard to flag bugs (view)
  • Places statistics collection (site, blog post)

Testing

  • Run Ts and Tp against constructed profiles (bug 489183)
  • Create a test framework for measuring and tracking performance of the user interface (bug fileme)

Hotspot Fixes

  • New tab
  • History menu (bug 490653, bug 488966)
  • History sidebar - last visited (bug 417262)
  • History sidebar - most visited
  • History sidebar - search
  • Bookmarks search

Timeline

Meeting Notes

Dec 2, 2008

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 ddahl bug 480340, bug 489183 ddahl created scripts for generating places dbs
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 bug 470379 Complete
fix dtrace js probes on trunk sayrer bug 468041, bug 469757
get a startup timeline cbartley bug 467953 talk to mobile & Taras work they've done on it