3,860
edits
No edit summary |
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...) |
||
(4 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
==Introduction== | ==Introduction== | ||
Currently, we have no | 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 | 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 | # 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 | ||
# Report the data into datazilla on a regular basis | # Report the data into datazilla on a regular basis | ||
==Bugs== | ==Bugs== | ||
The meta bug is - 990833 | The meta bug is - {{bug|990833}} | ||
== | ==Contacts== | ||
[https://mozillians.org/en-US/u/mchang/ Mason Chang] |
edits