diff options
author | Chris Wilson <chris@chris-wilson.co.uk> | 2009-06-13 08:24:22 +0100 |
---|---|---|
committer | Chris Wilson <chris@chris-wilson.co.uk> | 2009-06-13 08:24:22 +0100 |
commit | 1f542965f0310aed493651b8ddc1e98a4192b977 (patch) | |
tree | 21ee8eb642e939cd775f23993ebd3c4d318044fc /perf/README | |
parent | 3b6e4018c69f88135f8d937724acf90adb003bad (diff) | |
download | cairo-1f542965f0310aed493651b8ddc1e98a4192b977.tar.gz |
[perf] Mention cairo-perf-compare-backends in the README
Diffstat (limited to 'perf/README')
-rw-r--r-- | perf/README | 16 |
1 files changed, 16 insertions, 0 deletions
diff --git a/perf/README b/perf/README index fd6eb308d..0fc5281b7 100644 --- a/perf/README +++ b/perf/README @@ -132,6 +132,22 @@ those tests: ./cairo-perf-diff -f HEAD -- text +Generating comparisons of different backends +-------------------------------------------- +An alternate question that is often asked is, "how does the speed of one +backend compare to another?". cairo-perf-compare-backends can read files +generated by cairo-perf and produces a comparison of the backends for every +test. + +Again, by way of example: + + # Show relative performance of the backends + ./cairo-perf-compare-backends cairo.perf + +This will work whether the data files were generate in raw mode (with +cairo-perf -r) or cooked, (cairo-perf without -r). + + Creating a new performance test ------------------------------- This is where we could use everybody's help. If you have encountered a |