]> git.cworth.org Git - fips/commitdiff
TODO: Add some additional items suggested by Eero.
authorCarl Worth <cworth@cworth.org>
Fri, 14 Jun 2013 18:29:33 +0000 (11:29 -0700)
committerCarl Worth <cworth@cworth.org>
Fri, 14 Jun 2013 18:29:33 +0000 (11:29 -0700)
Again, simply trying to ensure that good ideas that come in via email
don't get dropped on the floor.

 Report shader compilation time.

+Report elapsed time per frame.
+
+Add options to control which metrics should be collected.
+
 Add Eric's tiny hash table for collecting per-shader statistics

  people.freedesktop.org:~anholt/hash_table
@@ -45,6 +49,9 @@ Infrastructure (larger-scale things, more future-looking items)

 Use ncurses for a better top-like display.

+Report timestamps and CPU time durations for operations causing
+CPU/GPU syncs.
+
 Emit per-frame data in a format for external timeline viewer.

 Allow enabling/disabling of tracing at run-time
@@ -61,10 +68,16 @@ should automatically collect:

 Audit exisiting visualization tools before writing one from scratch

- Eero suggested that pytimechart might be well-suited:
+ Eero suggested two possibilities:

+ pytimechart
+ -----------
  http://pythonhosted.org/pytimechart/index.html

+ e-graph
+ -------
+ https://gitorious.org/e-graph
+
  Others?

 Explore using perf/LTTng probing instead of LD_PRELOAD wrapper

TODO

diff --git a/TODO b/TODO
index 4a61c1ba9c6732208819d36d27ae42e6e5ed7d95..36b970916150f7747971b03e06ce4a0c20d61f03 100644 (file)
--- a/TODO
+++ b/TODO
@@ -28,6 +28,10 @@ Report GPU frequency per frame.
 
 Report shader compilation time.
 
+Report elapsed time per frame.
+
+Add options to control which metrics should be collected.
+
 Add Eric's tiny hash table for collecting per-shader statistics
 
        people.freedesktop.org:~anholt/hash_table
@@ -45,6 +49,9 @@ Infrastructure (larger-scale things, more future-looking items)
 
 Use ncurses for a better top-like display.
 
+Report timestamps and CPU time durations for operations causing
+CPU/GPU syncs.
+
 Emit per-frame data in a format for external timeline viewer.
 
 Allow enabling/disabling of tracing at run-time
@@ -61,10 +68,16 @@ should automatically collect:
 
 Audit exisiting visualization tools before writing one from scratch
 
-       Eero suggested that pytimechart might be well-suited:
+       Eero suggested two possibilities:
 
+               pytimechart
+               -----------
                http://pythonhosted.org/pytimechart/index.html
 
+               e-graph
+               -------
+               https://gitorious.org/e-graph
+
        Others?
 
 Explore using perf/LTTng probing instead of LD_PRELOAD wrapper