Firefox OS/Performance/Graphics Pipeline Instrumentation and Integration into the Cleopatra Profiler: Difference between revisions

Firefox OS/Performance/Graphics Pipeline Instrumentation and Integration into the Cleopatra Profiler (view source)

Revision as of 16:18, 9 May 2014

917 bytes added , 9 May 2014

no edit summary

Mchang

canmove, Confirmed users

58

edits

@@ Line 1: / Line 1: @@
 ==Introduction==
-A brief introduction on this project.  Describe scope and what to expect.
+Currently, when we profile the Compositor thread in the b2g process with the Gecko Profiler, https://developer.mozilla.org/en-US/docs/Mozilla/Performance/Profiling_with_the_Built-in_Profiler, we see a limited set of data. I'd like to introduce more detail into the Cleopatra Profiler that explains with some detail, why we have graphics issues. For example, some ideas are being implemented by Benoit Girard - http://benoitgirard.wordpress.com/
 ==Project Plan==
-Please put links here to any relevant documentation.
+The project consists of identifying the various stages in the pipeline, identifying cases where the graphics pipeline is slow and why, and finally instrumenting the Cleopatra profiler to identify common slow cases.
 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.
+# Identify slow paths in the graphics pipeline
+# Identify causes of the slow paths in the graphics pipeline
+# Create error messages and integrate the causes up to the Cleopatra profiler data
+# Modify the Cleopatra front end to display the data in a human readable way
+Some data that would be useful would be:
+) Touch input events and position - This would be useful for frame uniformity
+) Vsync events
+) APZC display port data
+) Current layer data
 ==Bugs==
@@ Line 14: / Line 23: @@
 ==Proposal==
-Link to any existing proposals here.
+http://benoitgirard.wordpress.com/ - For current work