Perfomatic: Difference between revisions
Jump to navigation
Jump to search
Line 68: | Line 68: | ||
* 1.0 Branch on Mercurial | * 1.0 Branch on Mercurial | ||
* [[Perfomatic:Rearchitecture | New Architecture Notes]] | * [[Perfomatic:Rearchitecture | New Architecture Notes]] | ||
* [[Media: | * [[Media:Graph_server_new_db_schema.jpg | New DB Schema]] | ||
* [[Perfomatic:API | API]] | * [[Perfomatic:API | API]] | ||
* [http://people.mozilla.org/~morgamic/graph-server-architecture.png Morgamic's Proposed Architecture] | * [http://people.mozilla.org/~morgamic/graph-server-architecture.png Morgamic's Proposed Architecture] |
Revision as of 23:16, 15 December 2008
People
- Ryan Doherty
- Les Orchard
- Alice Nodelman
- Chris Cooper
- Mark Smith
- Stephen Donner (QA)
- graphserver@mozilla.com
Milestones
- 1.0 bug list
- 0.6 bug list - done
- 0.5 bug list - Done
- 0.4 bug list - Done
- 0.3 bug list - Done
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
Schema Junk
Requirements
Servers
Tests
Source Code
- HG: http://hg.mozilla.org/index.cgi/graphs/
- CVS: http://lxr.mozilla.org/mozilla/source/webtools/new-graph/ (deprecated)
Installation Docs
Meetings
- Thursdays @ 11am
- 1-800-707-2533 (pin 369) or 1-650-215-1282 or 1-650-903-0800
- Conferencing Center: x91
- Conference ID: 300
- Meeting Notes
- IRC: #perfomatic
Rearchitecture
The current implementation of the graph server database is becoming the bottleneck for improvements. We have created a new database and API for retrieving data.
We are planning on migrating to the new architecture early in Q1.
- 1.0 Branch on Mercurial
- New Architecture Notes
- New DB Schema
- API
- Morgamic's Proposed Architecture
- Reworking how data to sent to the graph server
Backdrop
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.