Firefox:FrontEndPerformance: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
=Requirements=
=Current Activity=
 
We need an end-to-end approach to front-end performance, from detection to reporting to resolution to regression-catching.


Detection and Reporting:
Detection and Reporting:
* A new keyword for ui-responsiveness bugs?
* Mark UI performance bugs with [TSnap] in the whiteboard (current list)
* Extension for reporting beachballing, script hangs?
* Mark startup performance bugs with [TStartup] in the whiteboard ([current list])
 
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 (mozmill?) *or* in xpcshell
* reports to Tinderbox
* reports to graph server
** need to graph individual test scores over time
* [[Perfomatic#Rearchitecture|New Graph Server]] (work on hold until this is done)
** https://wiki.mozilla.org/Perfomatic:SendingData
 
=Proposal=
 
Research/Tracking
* Implement about:me reporting ({{bug|480154}})
* Implement about:me reporting ({{bug|480154}})
* Use [TSnappiness] whiteboard to flag bugs ([https://bugzilla.mozilla.org/buglist.cgi?quicksearch=tsnappiness view])
* Places statistics collection ([https://places-stats.mozilla.com/ site], [http://blog.mozilla.com/adw/2009/03/25/places-stats/ blog post])
* Places statistics collection ([https://places-stats.mozilla.com/ site], [http://blog.mozilla.com/adw/2009/03/25/places-stats/ blog post])
Testing
* Create extension for reporting beachballing, script hangs
 
Testing:
* Run Ts and Tp against constructed profiles ({{bug|489183}})
* Run Ts and Tp against constructed profiles ({{bug|489183}})
* Create a test framework for measuring and tracking performance of the user interface ({{bug|fileme}})
* Test framework for measuring and tracking performance of user interface actions ({{bug|fileme}})


Hotspot Fixes
Hotspot Fixes
* New tab
* New tab
* History menu ({{bug|490653}}, {{bug|488966}})
* History menu (<strike>{{bug|488966}}</strike>)
* History sidebar - search
* History sidebar - last visited ({{bug|417262}})
* History sidebar - last visited ({{bug|488966}})
* History sidebar - most visited
* History "older than 6 mos"
* History search
* Bookmarks search
* Bookmarks search
* Bookmarks backup
* Bookmarks restore


=Timeline=
=Timeline=

Latest revision as of 21:25, 3 June 2009

Current Activity

Detection and Reporting:

  • Mark UI performance bugs with [TSnap] in the whiteboard (current list)
  • Mark startup performance bugs with [TStartup] in the whiteboard ([current list])
  • Implement about:me reporting (bug 480154)
  • Places statistics collection (site, blog post)
  • Create extension for reporting beachballing, script hangs

Testing:

  • Run Ts and Tp against constructed profiles (bug 489183)
  • Test framework for measuring and tracking performance of user interface actions (bug fileme)

Hotspot Fixes

  • New tab
  • History menu (bug 488966)
  • History sidebar - last visited (bug 417262)
  • History sidebar - most visited
  • History "older than 6 mos"
  • History search
  • Bookmarks search
  • Bookmarks backup
  • Bookmarks restore

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