Performance/Status Meetings/2007-July-25: Difference between revisions

Performance/Status Meetings/2007-July-25 (view source)

119 bytes removed , 25 July 2007

m

using bug template, shoter url

151

edits

@@ Line 6: / Line 6: @@
 == Infrastructure ==
-* Generate reliable, relevant performance data (already underway as talos). Talos status update? http://tinderbox.mozilla.org/showbuilds.cgi?tree=MozillaTest
+* Generate reliable, relevant performance data (already underway as talos). Talos status update? http://tinderbox.mozilla.org/MozillaTest/
 ** running against hourly builds on trunk, see MozillaTest
 ** lots of crashes with historical runs, wondering if its doable.
@@ Line 28: / Line 28: @@
 ** Better reports for sheriffs to easily spot perf regressions
 ** Tracking down specific performance issues
-* stats change to track AUS usage by osversion. [https://bugzilla.mozilla.org/show_bug.cgi?id=382044 bug#382044]. '''AI:justin'''
+* stats change to track AUS usage by osversion. {{bug|382044}}. '''AI:justin'''
 *Priorities for infra:
@@ Line 44: / Line 44: @@
 ** vlad has data
-* pageload test rewrite ([https://bugzilla.mozilla.org/show_bug.cgi?id=387110 bug 387110])
+* pageload test rewrite ({{bug|387110}})
 ** since we have a chance at a clean break, we should look at how the composite scores are calculated
 ** do we still want to ignore the biggest value when computing the mean and stddev?  (there is caching and stuff that happens during the first time a page is loaded that ends up beneficially effecting subsequent page loads)