[cairo-commit] [cairo-www] src/FAQ.mdwn
cworth at freedesktop.org
Fri Jun 12 14:36:55 PDT 2009
src/FAQ.mdwn | 14 +++++++++++---
1 file changed, 11 insertions(+), 3 deletions(-)
Author: Carl Worth <cworth at cworth.org>
Date: Fri Jun 12 14:36:08 2009 -0700
FAQ: Add a couple more section headings regarding traces.
Otherwise we were talking about how to run cairo-perf-trace under
the "how to generate a trace" section which just wasn't right.
diff --git a/src/FAQ.mdwn b/src/FAQ.mdwn
index 632db15..8fe950c 100644
@@ -393,6 +393,8 @@ This eliminates the extra caller information from the trace, (which
reduces overhead when replaying), and compresses the output,
(decompress with the "lzma -cd").
+<h3>How to benchmark an existing trace:</h3>
To benchmark the performance of a trace, run:
$ cairo-perf-trace application.trace
@@ -400,9 +402,15 @@ To benchmark the performance of a trace, run:
which will replay the trace several times against multiple backends
and report the time required for replay against each backend.
+<h3>What traces has the community collected?</h3>
A compilation of "interesting" traces can be found in the
-repositroy](http://cgit.freedesktop.org/cairo-traces). By checking
-this repository out to perf/cairo-traces in the cairo source
-directory, these traces will be automatically run by
+repository](http://cgit.freedesktop.org/cairo-traces). This collection
+includes traces of various uses of common applications such as
+firefox, gnome-terminal, swfdec (including viewing youtube), and
+By checking this repository out to perf/cairo-traces in the cairo
+source directory, these traces will be automatically run by
"cairo-perf-trace" (with no arguments) as well as by "make perf".
More information about the cairo-commit