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

From MozillaWiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
==Introduction==
==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.
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==


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


# 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.
# 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.
Line 13: Line 13:


==Bugs==
==Bugs==
The meta bug is - 990833
The meta bug is - {{bug|990833}}

Revision as of 00:35, 10 May 2014

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

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