From: "René Scharfe" <rene.scharfe@lsrfire.ath.cx>
To: Michael Haggerty <mhagger@alum.mit.edu>
Cc: git@vger.kernel.org
Subject: Re: Is there a place for benchmarking scripts?
Date: Thu, 27 Oct 2011 18:01:40 +0200 [thread overview]
Message-ID: <4EA98064.3060706@lsrfire.ath.cx> (raw)
In-Reply-To: <4EA7D7E3.2020009@alum.mit.edu>
Am 26.10.2011 11:50, schrieb Michael Haggerty:
> I've been doing a lot of benchmarking of git performance in the presence
> of lots of references. I've written a few scripts to automate the
> benchmarking [1]. They are not beautiful and would require a couple of
> local adjustments [2,3]. They are too time-consuming to be made part of
> the usual test suite. I wouldn't want to commit to maintaining them.
> But they have certainly been useful to me, and they generate readable
> output [4].
>
> My question is: would such benchmarking scripts be welcome within the
> git project? If so, where should I put it? Is any benchmarking
> code/framework already in use?
That would be nice. A whole performance regression testing suite would
be even nicer and can perhaps be built piece by piece.
We have contrib/ and we have the test-* commands; t/ doesn't seem to fit
too well with its focus on OK or fail.
René
prev parent reply other threads:[~2011-10-27 16:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-26 9:50 Is there a place for benchmarking scripts? Michael Haggerty
2011-10-27 16:01 ` René Scharfe [this message]
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=4EA98064.3060706@lsrfire.ath.cx \
--to=rene.scharfe@lsrfire.ath.cx \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).