Auto-tools/Projects/Signal From Noise: Difference between revisions

(Created page with "= Signal From Noise = Making sense of the Talos results == Overview == Historically we have had an 'acceptable' range of fluctuation in our talos number. Our methods of manag...")
 
Line 51: Line 51:
* start investigating tp5 (or maybe it is time for tp6 and we start there)
* start investigating tp5 (or maybe it is time for tp6 and we start there)
* enhance compare talos toolchain to show differences from a try server run to the baseline (easier talos development as well as firefox development)
* enhance compare talos toolchain to show differences from a try server run to the baseline (easier talos development as well as firefox development)
== Related Work ==
We need to be considerate of other projects and try to coordinate as much as possible.
* mozbase
** we will be fixing up talos to use mozprocess, mozprofile, mozrunner.  This doesn't intersect with SfN work, but if we are doing a large staging run this would be beneficial to bundle together. staging
* mozharness
** again, no impact on this project. staging,SxS
* python 2.4->2.6+
** no real impact on this project. staging,SxS
* jetpack talos
** most likely some changes to talos, primarily focused on ts, maybe some graphserver work required
* AMO maintenance
** no impact on this project
* OSX RSS from pageloader
** small talos and config tweaks for tp5.  staging,SxS
== Possible Reshuffling ==
Most of the other work requires staging and side by side (SxS) running to ensure we don't fudge the numbers.
* Can our toolchain make the side by side easier and less painful?
We won't be modifying talos proper much which means that the work in these other projects shouldn't affect SfN. 
* Will we be comfortable doubling our work in staging and SxS?
Confirmed users
3,376

edits