Perfomatic: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
 
(72 intermediate revisions by 10 users not shown)
Line 1: Line 1:
= Backdrop =
= Summary =
The perfomatic is the Mozilla graph server, and is used to understand how multiple performance metrics change over time.  Grasping these relationships is important to understanding how the addition of multiple features affects all facets of speed and performance -- not just the bubbly marketing interpetation of performance -- the real "stuff that matters" kind of performance.


= Source Code =
The Mozilla graph server is used to understand how multiple performance metrics change over time. It is a web application for creating graphs of performance test results for a user-configurable combination of branch, operating system and machine.
* HG: http://hg.mozilla.org/index.cgi/graphs/
* CVS: http://lxr.mozilla.org/mozilla/source/webtools/graph/ (depricated)


= Meetings =
'''People'''
* Tentatively Fridays @ 10am (subject to change!)
* Rob Helmer (rhelmer), Alice Nodelman (anode), Laura Thomson (laura), Chris Howse (chowse)
* [[Perfomatic:Meeting_Notes|Meeting Notes]]
* IRC: [irc://irc.mozilla.org/#perfomatic #perfomatic]


= Infrastructure =
'''Bugs'''
So, maybe someone can add more to this, but here's morgamic's skewed view of where we should venture:
* [https://bugzilla.mozilla.org/enter_bug.cgi?product=Webtools&component=Graph%20Server File a bug in Webtools : Graph Server]
http://people.mozilla.org/~morgamic/graph-server-architecture.png
* [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=component%3A%22graph%20server%22 open bugs]
 
= Requirements =
* [http://wiki.mozilla.org/Perfomatic:Requirements Requirements and use-cases]
 
= Architecture =
 
'''Overview:'''
* [[Talos]] creates build
* Talos runs a test
* Sends data from test to:
** bulk.cgi - for multiple data points
** collect.cgi - for 1 data point
* bulk.cgi or collect.cgi input into mysql db
* graphs.mozilla.org/graphs.html
** displays a line graph of the data over time
* Single point on graph is an average(ish) of the tests on that day
 
'''Diagrams, etc'''
* [http://wiki.mozilla.org/Perfomatic:Schema_Notes Schema notes]
* [[Media:Graph_server_new_db_schema2.png | DB schema diagram]]
* [[Perfomatic:Rearchitecture | Architecture notes]]
* [http://people.mozilla.org/~morgamic/graph-server-architecture.png Morgamic's architecture diagram]
* [[Perfomatic:SendingData| How data is sent to the graph server]]
 
= Implementation =
 
* [http://hg.mozilla.org/graphs/ Source code]
* [[Perfomatic:UI | 2010 Interface redesign]]
* [[Perfomatic:API | API]]
* [[Perfomatic/Installation]]
* Tests
** [[Perfomatic/Test_Name_Mappings|Test Name Mappings]]
** [[Perfomatic/BFT|BFT]]
* Servers
** [http://graphs.mozilla.org/ Production Server]
** [http://graphs.allizom.org/ Stage Server]
*** [http://graphs-stage2.mozilla.org/graph.html#type=series Series data link]

Latest revision as of 19:09, 11 September 2012

Summary

The Mozilla graph server is used to understand how multiple performance metrics change over time. It is a web application for creating graphs of performance test results for a user-configurable combination of branch, operating system and machine.

People

  • Rob Helmer (rhelmer), Alice Nodelman (anode), Laura Thomson (laura), Chris Howse (chowse)
  • IRC: #perfomatic

Bugs

Requirements

Architecture

Overview:

  • Talos creates build
  • Talos runs a test
  • Sends data from test to:
    • bulk.cgi - for multiple data points
    • collect.cgi - for 1 data point
  • bulk.cgi or collect.cgi input into mysql db
  • graphs.mozilla.org/graphs.html
    • displays a line graph of the data over time
  • Single point on graph is an average(ish) of the tests on that day

Diagrams, etc

Implementation