|
|
| Line 5: |
Line 5: |
| == Infrastructure == | | == Infrastructure == |
| == Agenda == | | == Agenda == |
| * Generate reliable, relevant performance data (already underway as talos). Talos status update?
| |
| http://tinderbox.mozilla.org/showbuilds.cgi?tree=MozillaTest
| |
|
| |
| * Areas where help is needed
| |
| * expand the scope of performance testing beyond Ts/Tp/TXUL/TDHMTL
| |
| * reduce noise in tests to ~1% (suggested by bz, not started)
| |
| * move perf tests to chrome, so we get more reliable results, and can test more than just content
| |
| * improve performance reporting and analyses:
| |
| ** Better reports for sheriffs to easily spot perf regressions
| |
| ** Tracking down specific performance issues
| |
| * stats change to track AUS usage by osversion.
| |
|
| |
| *Priorities for infra:
| |
| ** Generate historical baselines
| |
| ** General profile data regularly on builds
| |
| ** Getting the perf numbers more stable
| |
| ** Developing the graph server to display time spent in each module
| |
|
| |
| * New ideas
| |
| ** Question: How are we tracking perf bugs, specifically, and are we doing this the same way we are triaging security bugs? Can we do it the same way if not? (damon)
| |
|
| |
|
| == Gecko: Perf discussion == | | == Gecko: Perf discussion == |