Please view live action play by play notes on [etherpad]

Previous Action Items

[jmaher/kyle] - start work on refining automated regression detection
[jeads] - initial v1 of the timeline/pushed based history graphs for overall job status and page status.

Milestone 1

[Bug List: ]
[DONE] Create email list for results from datazilla
Wire emailing to that ^ list into the talos emailer (analyze_talos.py) now
Create schema and data service for generating the relevant time course data for comparisons of:
- Same page perf to same page perf over pushes and/or time (identifying noise in page)
- Same page perf to same page perf on different platforms over pushes and/or time (platform differences)
- Page set perf to page set perf on same platform over pushes and/or time (what graph server now shows)
- Page set perf to page set perf on different platforms over pushes and/or time (what graph server now shows with some poking)
- Data set ingestion rates per test per platform (ensuring we are getting the data)
- Page and pageset perf per machine per platform (identifying specific machine anomalies)
Begin analyzing data to optimize statistics for regression detection on each desktop Talos test (we are pretty good for tp5o, we need to look into Ts, Tsvg* and others)
- Understand if we need per-page optimizations as well for pages within pagesets (we likely do).
[DONE] Analyze why we seem to not get data at times from certain platform/tree combinations.

BenWa has proposed adding thresholds per test to the tree, everything outside the threshold would be orange and require a perf sherriff to adjust the value. (carry over)

we should still consider looking at the hardware pool
- Consider splitting hardware pool
- Consider running talos on a few builds on a set of machines over and over to see what noise metrics we get (see how much noise is based on differences in machines versus in the build and install of the product)