Firefox OS/Performance/Graphics Performance Automation: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Created page with "==Introduction== A brief introduction on this project. Describe scope and what to expect. ==Project Plan== Please put links here to any relevant documentation. To be suc...")
 
No edit summary
Line 1: Line 1:
==Introduction==
==Introduction==


A brief introduction on this project.  Describe scope and what to expect.
Currently, we have no grahpics automation in place. We are in the process of spinning them up, but there is a lot of work to be done. The objective of this project is to measure various aspects of the Graphics pipeline and set up automation to report the data to datazilla.


==Project Plan==
==Project Plan==


Please put links here to any relevant documentation.  
There are various stages and indicators to inform us that the Graphics pipeline is working well. The general step will be to:
 
# Identify and instrument Gecko to detail how long a stage in the Graphics Pipeline takes
# Extract the measurement and output it to JSON or some datazilla compatible format
# Create a test case to use the extracted data
# Report the data into datazilla on a regular basis


To be successful in this project, the following has to be accomplished:
# Please enumerate a rough checklist for what must be accomplished to be successful.


==Bugs==
==Bugs==
Link to any existing bugs here.
The meta bug is - 990833


==Proposal==
==Proposal==
Link to any existing proposals here.
Link to any existing proposals here.

Revision as of 15:56, 9 May 2014

Introduction

Currently, we have no grahpics automation in place. We are in the process of spinning them up, but there is a lot of work to be done. The objective of this project is to measure various aspects of the Graphics pipeline and set up automation to report the data to datazilla.

Project Plan

There are various stages and indicators to inform us that the Graphics pipeline is working well. The general step will be to:

  1. Identify and instrument Gecko to detail how long a stage in the Graphics Pipeline takes
  2. Extract the measurement and output it to JSON or some datazilla compatible format
  3. Create a test case to use the extracted data
  4. Report the data into datazilla on a regular basis


Bugs

The meta bug is - 990833

Proposal

Link to any existing proposals here.

Retrieved from "https://wiki.allizom.org/index.php?title=Firefox_OS/Performance/Graphics_Performance_Automation&oldid=975312"