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...")
 
m (Lakrits moved page FirefoxOS/Performance/Graphics Performance Automation to Firefox OS/Performance/Graphics Performance Automation: The official spelling of "Firefox OS" leaves a space between the two parts of the name. It's easier to find a pa...)
 
(5 intermediate revisions by 3 users not shown)
Line 1: Line 1:
==Introduction==
==Introduction==


A brief introduction on this project.  Describe scope and what to expect.
Currently, we have no graphics 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 [http://datazilla.mozilla.org/b2g/ 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 steps will be to:


To be successful in this project, the following has to be accomplished:
# Identify and instrument Gecko to detail how long a stage in the Graphics Pipeline takes. Notable stages would be layout flushes, painting, building display lists, and checkerboarding.
# Please enumerate a rough checklist for what must be accomplished to be successful.
# 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


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


==Proposal==
==Contacts==
Link to any existing proposals here.
[https://mozillians.org/en-US/u/mchang/ Mason Chang]

Latest revision as of 13:59, 1 February 2015

Introduction

Currently, we have no graphics 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 steps will be to:

  1. Identify and instrument Gecko to detail how long a stage in the Graphics Pipeline takes. Notable stages would be layout flushes, painting, building display lists, and checkerboarding.
  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 - bug 990833

Contacts

Mason Chang

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