Performance/Status Meetings/2007-June-06: Difference between revisions

Line 7: Line 7:
== Agenda ==
== Agenda ==


* Choosing time/frequency of meeting: 10am-11am?
* Choosing time/frequency of meeting: 10am-11am? Every week?
* Talos status  
* Generate reliable, relevant performance data (already underway as talos). Talos status update?
* Graph server status
* Graph server status
* Areas where help is needed
* Areas where help is needed
* Reducing test variance
* Reducing test variance
* New ideas


Agenda:
* Extending meeting? Maybe 10-11?
* generate reliable, relevant performance data (already underway as talos)
* expand the scope of performance testing beyond Ts/Tp/TXUL/TDHMTL
* expand the scope of performance testing beyond Ts/Tp/TXUL/TDHMTL
* reduce noise in tests to ~1% (suggested by bz, not started)
* reduce noise in tests to ~1% (suggested by bz, not started)
* run performance tests with profiling on (rhelmer set up a machine
* run performance tests with profiling on (rhelmer set up a machine for this, but jprof has problems on trunk)
for this, but jprof has problems on trunk)
* move perf tests to chrome, so we get more reliable results, and
* move perf tests to chrome, so we get more reliable results, and
can test more than just content
can test more than just content
Line 29: Line 22:
* Better reports for sheriffs to easily spot perf regressions
* Better reports for sheriffs to easily spot perf regressions
* Tracking down specific performance issues
* Tracking down specific performance issues
* stats change to track AUS usage by osversion.
* New ideas


== Action Items ==
== Action Items ==
Confirmed users
2,679

edits