From: Thomas Rast <trast@student.ethz.ch>
To: <git@vger.kernel.org>
Cc: Michael Haggerty <mhagger@alum.mit.edu>
Subject: [RFC PATCH 0/4] Performance test framework
Date: Wed, 14 Dec 2011 16:23:28 +0100 [thread overview]
Message-ID: <cover.1323876121.git.trast@student.ethz.ch> (raw)
Hi,
This is the first shot at a usable performance test suite. It's
another angle than the refperf work of Michael Haggerty, however he
helped shape this in #git-devel (thanks!).
There's a big README, but if you just want to dive in, here's me
comparing the grep performance of my POC "pack reading in parallel"
branch against Junio's next:
$ cd t/perf
$ ./run origin/next t/sha1_file-parallel p7810-grep.sh
[snip no-op compilation]
=== Running 1 tests in build/7a6d658aa3c9016dd04ff3515cbf15edca6562a4 ===
perf 1 - grep worktree, cheap regex: 1 2 3 4 5 ok
perf 2 - grep worktree, expensive regex: 1 2 3 4 5 ok
perf 3 - grep --cached, cheap regex: 1 2 3 4 5 ok
perf 4 - grep --cached, expensive regex: 1 2 3 4 5 ok
# passed all 4 test(s)
1..4
GIT_VERSION = 1.7.8.GIT
* new build flags or prefix
* new link flags
GEN common-cmds.h
CC hex.o
CC kwset.o
[snip rest of compilation]
=== Running 1 tests in build/dd2bf650b382f5aca727b7d93a48598fb1a2f7d9 ===
perf 1 - grep worktree, cheap regex: 1 2 3 4 5 ok
perf 2 - grep worktree, expensive regex: 1 2 3 4 5 ok
perf 3 - grep --cached, cheap regex: 1 2 3 4 5 ok
perf 4 - grep --cached, expensive regex: 1 2 3 4 5 ok
# passed all 4 test(s)
1..4
Test origin/next t/sha1_file-parallel
----------------------------------------------------------------------------------
7810.1: grep worktree, cheap regex 0.16(0.16+0.35) 0.16(0.15+0.36) +0.0%
7810.2: grep worktree, expensive regex 7.83(29.68+0.39) 7.95(29.98+0.39) +1.5%
7810.3: grep --cached, cheap regex 3.12(3.11+0.24) 1.11(3.46+0.18) -64.4%
7810.4: grep --cached, expensive regex 9.43(30.53+0.28) 8.89(32.99+0.22) -5.7%
Note in particular that neither of the two branches contains the perf
work.
Have fun!
Thomas Rast (4):
Move the user-facing test library to test-lib-functions.sh
test-lib: allow testing another git build tree
Introduce a performance testing framework
Add a performance test for git-grep
Makefile | 26 ++-
t/Makefile | 5 +-
t/perf/.gitignore | 2 +
t/perf/Makefile | 15 +
t/perf/README | 146 ++++++++++
t/perf/aggregate.perl | 166 ++++++++++++
t/perf/min_time.perl | 21 ++
t/perf/p0000-perf-lib-sanity.sh | 41 +++
t/perf/p0001-rev-list.sh | 17 ++
t/perf/p7810-grep.sh | 23 ++
t/perf/perf-lib.sh | 199 ++++++++++++++
t/perf/run | 82 ++++++
t/test-lib-functions.sh | 528 ++++++++++++++++++++++++++++++++++++
t/test-lib.sh | 561 +++------------------------------------
14 files changed, 1300 insertions(+), 532 deletions(-)
create mode 100644 t/perf/.gitignore
create mode 100644 t/perf/Makefile
create mode 100644 t/perf/README
create mode 100755 t/perf/aggregate.perl
create mode 100755 t/perf/min_time.perl
create mode 100755 t/perf/p0000-perf-lib-sanity.sh
create mode 100755 t/perf/p0001-rev-list.sh
create mode 100755 t/perf/p7810-grep.sh
create mode 100644 t/perf/perf-lib.sh
create mode 100755 t/perf/run
create mode 100644 t/test-lib-functions.sh
--
1.7.8.304.ge42e4
next reply other threads:[~2011-12-14 15:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 15:23 Thomas Rast [this message]
2011-12-14 15:23 ` [RFC PATCH 1/4] Move the user-facing test library to test-lib-functions.sh Thomas Rast
2011-12-14 15:23 ` [RFC PATCH 2/4] test-lib: allow testing another git build tree Thomas Rast
2011-12-15 3:07 ` Junio C Hamano
2011-12-15 10:33 ` Thomas Rast
2011-12-15 19:05 ` Junio C Hamano
2011-12-14 15:23 ` [RFC PATCH 3/4] Introduce a performance testing framework Thomas Rast
2011-12-14 16:04 ` Thomas Rast
2011-12-14 15:23 ` [RFC PATCH 4/4] Add a performance test for git-grep Thomas Rast
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1323876121.git.trast@student.ethz.ch \
--to=trast@student.ethz.ch \
--cc=git@vger.kernel.org \
--cc=mhagger@alum.mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.