From: "Torsten Bögershausen" <tboegi@web.de>
To: "David Turner" <dturner@twopensource.com>,
"Torsten Bögershausen" <tboegi@web.de>
Cc: Duy Nguyen <pclouds@gmail.com>,
Git Mailing List <git@vger.kernel.org>,
Junio C Hamano <gitster@pobox.com>,
Michael Haggerty <mhagger@alum.mit.edu>,
David Turner <dturner@twitter.com>
Subject: Re: [PATCH v6 2/2] refs.c: SSE4.2 optimizations for check_refname_component
Date: Thu, 05 Jun 2014 14:30:17 +0200 [thread overview]
Message-ID: <539062D9.60000@web.de> (raw)
In-Reply-To: <1401916560.18134.167.camel@stross>
On 2014-06-04 23.16, David Turner wrote:
>
> Sure! I actually went with > 120k to make measurement easier:
> https://github.com/dturner-tw/many-refs
Hm, I didn't get so man
git remote -v
origin https://github.com/dturner-tw/many-refs
wc .git/packed-refs
750 1130 38868 .git/packed-refs
time git rev-parse HEAD
7ac416f789fd4f1e398449113f6e1ec1d699141a
real 0m0.008s
user 0m0.002s
sys 0m0.004s
where only patch 1/2 doesn't seem to speed up things on my system:
time ~/projects/git/tb.140604_DavidTurner_SSE4/git rev-parse HEAD
7ac416f789fd4f1e398449113f6e1ec1d699141a
real 0m0.010s
user 0m0.002s
sys 0m0.005s
Intel Core Duo @ 2.4 Ghz, Mac OS
(and I get similar values under an AMD Dual core running 2Ghz under Linux)
next prev parent reply other threads:[~2014-06-05 12:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-04 3:38 [PATCH v6 1/2] refs.c: optimize check_refname_component() David Turner
2014-06-04 3:38 ` [PATCH v6 2/2] refs.c: SSE4.2 optimizations for check_refname_component David Turner
2014-06-04 8:04 ` Torsten Bögershausen
2014-06-04 11:21 ` Duy Nguyen
2014-06-04 14:25 ` Torsten Bögershausen
2014-06-04 21:16 ` David Turner
2014-06-05 12:30 ` Torsten Bögershausen [this message]
2014-06-05 12:58 ` Ondřej Bílka
2014-06-05 19:26 ` David Turner
2014-06-05 21:42 ` Torsten Bögershausen
2014-06-05 22:02 ` David Turner
2014-06-04 21:14 ` David Turner
2014-06-04 21:46 ` Junio C Hamano
2014-06-05 19:27 ` David Turner
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=539062D9.60000@web.de \
--to=tboegi@web.de \
--cc=dturner@twitter.com \
--cc=dturner@twopensource.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mhagger@alum.mit.edu \
--cc=pclouds@gmail.com \
/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.