From: Stefan Beller <stefanbeller@googlemail.com>
To: Thomas Rast <trast@inf.ethz.ch>
Cc: git@vger.kernel.org, peff@peff.net
Subject: Re: [PATCH] lookup_object: split up displacement penalty for hash collisions
Date: Fri, 16 Aug 2013 11:41:07 +0200 [thread overview]
Message-ID: <520DF3B3.3050900@googlemail.com> (raw)
In-Reply-To: <8761v6dm0r.fsf@linux-k42r.v.cablecom.net>
[-- Attachment #1: Type: text/plain, Size: 1922 bytes --]
On 08/16/2013 11:26 AM, Thomas Rast wrote:
> Thomas Rast <trast@inf.ethz.ch> writes:
>
>> Stefan Beller <stefanbeller@googlemail.com> writes:
>>
>>> However please do check if this patch brings the promised performance
>>> on your own, as you're likely using different hardware and another
>>> software setup. Feel free to share your performance differences.
>>
>> I get this on an i7-M620 laptop from t/perf/p0001-rev-list.sh:
>>
>> Test HEAD next
>> -------------------------------------------------------------------------------
>> 0001.1: rev-list --all 6.29(6.03+0.22) 6.33(6.06+0.24) +0.6%
>> 0001.2: rev-list --all --objects 53.22(52.48+0.54) 54.90(54.15+0.55) +3.2%*
>> -------------------------------------------------------------------------------
>> Significance hints: '.' 0.1 '*' 0.05 '**' 0.01 '***' 0.001
> [...]
>> I trust the laptop numbers less because it has far more thermal (and
>> thus throttling) issues, but the runs do show a significant difference,
>> though less than you claimed.
>
> Well, as I feared... another run on the same laptop:
>
> Test HEAD next
> ------------------------------------------------------------------------------
> 0001.1: rev-list --all 6.41(6.14+0.24) 6.36(6.10+0.23) -0.9%*
> 0001.2: rev-list --all --objects 54.60(53.84+0.55) 54.23(53.50+0.53) -0.7%
> ------------------------------------------------------------------------------
> Significance hints: '.' 0.1 '*' 0.05 '**' 0.01 '***' 0.001
>
I did some more tests as well, and I seem to have just been lucky with
the results initially posted. Now I got a negative impact as well on one
test, so that patch is not worth for includsion.
Thanks,
Stefan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 899 bytes --]
next prev parent reply other threads:[~2013-08-16 9:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-15 19:35 [PATCH] lookup_object: split up displacement penalty for hash collisions Stefan Beller
2013-08-16 8:28 ` Thomas Rast
2013-08-16 9:26 ` Thomas Rast
2013-08-16 9:41 ` Stefan Beller [this message]
2013-08-16 9:57 ` Jeff King
2013-08-16 13:49 ` Jeff King
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=520DF3B3.3050900@googlemail.com \
--to=stefanbeller@googlemail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=trast@inf.ethz.ch \
/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).