MozillaWiki

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

Page Discussion

Auto-tools/Projects/Signal From Noise (view source)

Revision as of 22:33, 6 December 2013

4,227 bytes removed ,  6 December 2013
→‎Meetings
(→‎Bugs: add link to fixed bugs)
 
(27 intermediate revisions by 4 users not shown)
Line 3: Line 3:
Making sense of the Talos results  
Making sense of the Talos results  


This is a joint project among the A-team, Releng, Webdev, and Metrics.
[[Auto-tools/Projects/SfN_2013Q2|Specifc goals 2013Q2]]


== Overview  ==
== Overview  ==
Line 10: Line 10:


We want to do a better job of generating our 1 tracking number. We also want to revisit the way we are testing things and make sure we are running the right tests and the correct number of iterations to get a reliable data point. Most likely this involves looking at every page that we have and tracking that page individually, not as a small piece of a larger set of pages.  
We want to do a better job of generating our 1 tracking number. We also want to revisit the way we are testing things and make sure we are running the right tests and the correct number of iterations to get a reliable data point. Most likely this involves looking at every page that we have and tracking that page individually, not as a small piece of a larger set of pages.  
Most of this project is outlined well at on the [[https://wiki.mozilla.org/Metrics/Talos_Investigation Talos Investigation]] page.


=== Goals  ===
=== Goals  ===


*define what is signal and what is noise  
Original Goals:
*understand the distribution of numbers and have confidence that our representation is meaningful
* define what is signal and what is noise  
 
* understand the distribution of numbers and have confidence that our representation is meaningful
=== Bugs  ===
 
Signal from Noise bugs are marked with the [https://bugzilla.mozilla.org/buglist.cgi?esolution=---&status_whiteboard_type=allwordssubstr&query_format=advanced&status_whiteboard=%5bSfN%5d SfN whiteboard entry]


Fixed signal from noise bugs: https://bugzilla.mozilla.org/buglist.cgi?list_id=5017261;resolution=FIXED;status_whiteboard_type=allwordssubstr;query_format=advanced;status_whiteboard=[SfN]
Appended goals:
* ensure our tests are testing the right things
* return performance regression results per push and posted to tbpl in real time
* provide tools to quickly investigate performance regressions, compare changesets/branches, and identify trends


== Drivers  ==
== Drivers  ==


*side by side staging : jmaher
* Datazilla: jeads
*graphserver : jeads + BYK
* Talos: jhammel, jmaher
*pageloader and other tools : jhammel
* Metrics: christina (as needed)
 
== Background  ==
 
Most of this project is outlined well at on the [[https://wiki.mozilla.org/Metrics/Talos_Investigation Talos Investigation]] page.


== Meetings  ==
== Meetings  ==
Meetings are every other [http://arewemeetingyet.com/Los%20Angeles/2013-12-19/11:00/b/Signal%20From%20Noise Thursday at 11AM Pacific Time] in Joel Maher's Vidyo room.


Meetings are every [http://www.timeanddate.com/worldclock/fixedtime.html?iso=20120308T11&p1=900 Thursday at 11AM Pacific Time].
* Notes from the status [https://wiki.mozilla.org/Auto-tools/Projects/Signal_From_Noise/Meetings meetings] are now on the the [[https://etherpad.mozilla.org/SignalFromNoise etherpad]].
 
[https://wiki.mozilla.org/Auto-tools/Projects/Signal_From_Noise/Meetings Here is our meeting page - take a look for more details and notes from previous meetings.]  
 
=== Datazilla Meetings  ===
 
The Datazilla project is holding focus group meetings with interested developers to judge our progress toward fixing use cases that developers and tree sheriffs care about.
 
See our [[Auto-tools/Projects/Datazilla/Meetings|Datazilla Meeting Page]] for information and notes from those.  
 
== Action Items  ==


The Goal by March 2012 is:
* The Datazilla project is holding [[Auto-tools/Projects/Datazilla/Meetings|Datazilla focus group meetings]] with interested developers to judge our progress toward fixing use cases that developers and tree sheriffs care about.


*Have the tools (pageloader, talos, graphserver) retooled so we can research new tests and run tests in a more reliable fashion
== Status ==
*Implement and roll out tdhtml using the new toolchain
* Performance Testing Reports:
*Have a process in place for adding new tests and pagesets into the tool set
** November 2011 - [[Auto-tools/Projects/Signal_From_Noise/StatusNovember2011]]
** November 2012 - [[Auto-tools/Projects/Signal_From_Noise/StatusNovember2012]]
** 2012 Execution - [[Auto-tools/Projects/Signal_From_Noise/Execution2012]]


There are general estimates of time throughout here, these are just placeholders. While the development time might be 2 hours, there are 2 days budgeted for this. Basically this accounts for time to develop, test and document your patch. Time for the reviewer to review and any back and forth. Finally time for staging and coordinating a deployment of a new talos.zip.  
== Bugs  ==
* Signal from Noise bugs are marked with the [https://bugzilla.mozilla.org/buglist.cgi?esolution=---&status_whiteboard_type=allwordssubstr&query_format=advanced&status_whiteboard=%5bSfN%5d SfN whiteboard entry]
* Fixed signal from noise bugs: https://bugzilla.mozilla.org/buglist.cgi?list_id=5017261;resolution=FIXED;status_whiteboard_type=allwordssubstr;query_format=advanced;status_whiteboard=[SfN]


All in all there are 82 estimated work days to achieve success this next quarter. These 82 days do not include core development of the graph server, but it does include us meeting, reviewing, and helping the UI folks with the graph server.
== UI (Datazilla)  ==


=== Milestone 1  ===
* original mockups: [[Media:TalosSignalFromNoiseMocks.pdf]].  
 
25 work days
 
*discard the first iteration of a page load (2 days to get landed, then SxS for a rollout - good practice) (jhammel - it would be nice to know *why* the difference)
*add options to pageloader for alternative page loading and measurements. make it more flexible as to how to load pages (the order, etc) 1 week
*add options to talos configuration to support new pageloader requirements. 2 days (jhammel - I wouldn't mind taking this)
*create a v1 of the dhtml test using new methodology. 1 week
*work with rhelmer and jeads to start discussion of what data we want. 2 weeks
**samples of work that :slewchuk did, mixed with inital data from dhtml results
*Initial version of database requirements to host new data. 3 days
*Blog frequently about progress and goals. get the word out. get feedback. cultivate knowledge
 
=== Milestone 2  ===
 
20 days of work
 
*Validate tdhtml data with metrics. 2 days
*Generate single 'metric' to track tdhtml as we currently do. 2 days
*Ensure core database and input methods for data are deployed. 2 days
*Start rolling out on branches with side by side staging. 4 days
*Beta version of UI live for inital data from the branches. 1 week
*Start investigating tsvg and a11y for optimal sampling sizes and accuracy. 1 week
*Continue to blog and post to newsgroups. n/a
 
=== Milestone 3  ===
 
24 work days
 
*Continue rolling out tdhtml to other branches. 4 days
*Enhance tools like compare-talos and regression-finder to work with new tdhtml. 1 week
*Write analysis toolchain for investigating new tests and pages (i.e. the work we do on tsvg and a11y should be automated). 1 week
*Integrate analysis toolchain into existing tools as much as possible. 1 week
*Version 1.0 of the new UI should be available. Multiple views on the same data as well as drill down from given data point or time window. 1 week
 
=== Milestone 3.14 (bonus work if all goes well)  ===
 
13 work days
 
*Define requirements for a Version 2.0 of the new UI. 2 days
*start rolling out tsvg and a11y. 3 days
*start investigating tp5 (or maybe it is time for tp6 and we start there). 1 week.
*enhance compare talos toolchain to show differences from a try server run to the baseline (easier talos development as well as firefox development). 3 days
 
== 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? (jhammel - this would be a good thing to blog about)
 
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? (jhammel - we should probably peg more carefully to versions of mozbase software)
 
== Contacts  ==
 
*ateam: BYK, jeads, jhammel, jmaher
*metrics: christina
*releng: armenzg ??
*webdev: rhelmer
 
== UI Prototype  ==
 
The prototype user interface can be reached on Mozilla-MPT by adding:
 
10.8.73.31 datazilla
 
To your /etc/hosts file and then directing your browser to:
 
/datazilla/views
 
The source code for datazilla can be found at https://github.com/jeads/datazilla
 
=== Mockups  ===
 
A set of user interface mockups can be found here [[Media:TalosSignalFromNoiseMocks.pdf]]. This document presents a collection of ideas for extending the graphs-new interface to manage different types of data with multiple visualization strategies.  


=== Use Cases  ===
=== Use Cases  ===
Line 186: Line 87:
=== Data  ===
=== Data  ===


Graph Server:
Current:  
Current:  


*data from tests (tp5 sample)  
*data from tests (tp5 sample)  
**noisy output on test console (coming from pageloader)
**noisy output on console (coming from pageloader)


  NOISE: |i|pagename|median|mean|min|max|runs|
  NOISE: |i|pagename|median|mean|min|max|runs|
Line 204: Line 106:
*TODO* define the perf counters that we collect and upload.
*TODO* define the perf counters that we collect and upload.


*how it is stored
Datazilla:
*volume
* volume - TODO
 
* storage - TODO
Proposed
* format - TODO
 
*data from tests
*how it is stored
*volume
 
[[Auto-tools/Projects/Signal From Noise/JSON Ingestion]]
(jhammel - I have no idea why the above useless page is linked to; it should be deleted and the link removed
 
== Data  ==
 
*http://people.mozilla.org/~jmaher/sfn/column/
*http://people.mozilla.org/~jmaher/sfn/row/


== Links  ==
== Links  ==
Line 240: Line 130:
* http://datazilla.readthedocs.org/en/latest/
* http://datazilla.readthedocs.org/en/latest/
* https://github.com/mozilla/datazilla-metrics
* https://github.com/mozilla/datazilla-metrics
 
* https://wiki.mozilla.org/images/d/dd/Talos_Statistical_Analysis_Writeup.pdf
* http://www.stat.purdue.edu/~doerge/BIOINFORM.D/FALL06/Benjamini%20and%20Y%20FDR.pdf
* https://wiki.mozilla.org/images/3/38/Tp5_Good_Pages.pdf : The Good Pages
* http://people.mozilla.org/~ctalbert/TalosPlots/rowmajor_change/index.html
* https://wiki.mozilla.org/images/2/2c/Plots.pdf : 40 pagecycles time series plots
* https://wiki.mozilla.org/images/e/e0/40_page_loads.pdf : 40 pagecycles time series plots
* http://plasma.cs.umass.edu/emery/stabilizer : Stabilizer is a compiler and runtime system that enables statistically rigorous performance evaluation.


=== Thesis  ===
=== Thesis  ===


*https://wiki.mozilla.org/images/c/c0/Larres-thesis.pdf, a mirror of http://majutsushi.net/stuff/thesis.pdf
*https://wiki.mozilla.org/images/c/c0/Larres-thesis.pdf, a mirror of http://majutsushi.net/stuff/thesis.pdf
Glob
Confirmed users
1,212

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/489337...782609"