Linaro Graphics Miscellany

Making profiling data user-friendly

Registered by Jesse Barker

We would like to have an easy way to make sense out of the data we will collect from profiling and benchmarking. Some of this is API trace data, for which it would be nice to have a common format. Some of this is determining the best way to present the data to the user so that it is meaningful.

Blueprint information

Status:
Complete
Approver:
Jesse Barker
Priority:
Medium
Drafter:
Alexandros Frantzis
Direction:
Needs approval
Assignee:
Alexandros Frantzis
Definition:
Obsolete
Series goal:
Accepted for trunk
Implementation:
Unknown
Milestone target:
milestone icon backlog
Completed by
Ilias Biris

Related branches

Sprints

Whiteboard

(?)

Work Items

Work items:
Evaluate extant profiling tools (perf, ftrace, oprofile, etc.) to see how they are presenting data: TODO
Evaluate "kernel shark" to see GUI frontend (GTK based): TODO
Evaluate "common trace format": TODO
Determine if BuGLe supports GLES 2.0: TODO
Fix on a particular trace format: TODO
Fix on a special-purpose user interface for the duration of this cycle (prototype to be spec'd): TODO
Determine interesting statistics: TODO
Define use cases for user experience: TODO

Dependency tree

* Blueprints in grey have been implemented.

Nearby

This blueprint contains Public information 
Everyone can see this information.