Firefox OS/Performance/Graphics Performance Automation: Difference between revisions
< Firefox OS | Performance
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 7: | Line 7: | ||
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 step will be to: | ||
# Identify and instrument Gecko to detail how long a stage in the Graphics Pipeline takes | # 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. | ||
# Extract the measurement and output it to JSON or some datazilla compatible format | # Extract the measurement and output it to JSON or some datazilla compatible format | ||
# Create a test case to use the extracted data | # Create a test case to use the extracted data | ||
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:
- 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.
- 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
The meta bug is - 990833