diff options
author | David Schleef <ds@schleef.org> | 2010-08-10 02:37:38 +0200 |
---|---|---|
committer | Benjamin Otte <otte@redhat.com> | 2010-08-10 02:37:38 +0200 |
commit | 73470862cbc5895147d5c58ca2647f539e8fe67c (patch) | |
tree | cf51c2b3d442492a60e61390393cf36ec6a0e4f5 /perf | |
parent | df8f96423429915ef1648310fce8b5aed0917c0a (diff) |
perf: Fix README to say cairo-perf-micro
Diffstat (limited to 'perf')
-rw-r--r-- | perf/README | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/perf/README b/perf/README index 0fc5281b..b142e59b 100644 --- a/perf/README +++ b/perf/README @@ -22,19 +22,19 @@ feel as to whether cairo is faster for everyday use. Running the micro-benchmarks ---------------------------- The micro-benchmarks are compiled into a single executable called -cairo-perf, which is what "make perf" executes. Some +cairo-perf-micro, which is what "make perf" executes. Some examples of running it: # Report on all tests with default number of iterations: - ./cairo-perf + ./cairo-perf-micro # Report on 100 iterations of all gradient tests: - ./cairo-perf -i 100 gradient + ./cairo-perf-micro -i 100 gradient # Generate raw results for 10 iterations into cairo.perf - ./cairo-perf -r -i 10 > cairo.perf + ./cairo-perf-micro -r -i 10 > cairo.perf # Append 10 more iterations of the paint test - ./cairo-perf -r -i 10 paint >> cairo.perf + ./cairo-perf-micro -r -i 10 paint >> cairo.perf Raw results aren't useful for reading directly, but are quite useful when using cairo-perf-diff to compare separate runs (see more @@ -47,7 +47,7 @@ The macro-benchmarks are run by a single program called cairo-perf-trace, which is also executed by "make perf". cairo-perf-trace loops over the series of traces stored beneath cairo-traces/. cairo-perf-trace produces the same output and takes the -same arguments as cairo-perf. Some examples of running it: +same arguments as cairo-perf-micro. Some examples of running it: # Report on all tests with default number of iterations: ./cairo-perf-trace |