From: Martin Fick <mfick@codeaurora.org>
To: Michael Haggerty <mhagger@alum.mit.edu>
Cc: git@vger.kernel.org
Subject: Re: Scalable reference handling
Date: Fri, 7 Oct 2011 12:51:43 -0600 [thread overview]
Message-ID: <201110071251.44052.mfick@codeaurora.org> (raw)
In-Reply-To: <4E8F2012.90108@alum.mit.edu>
On Friday, October 07, 2011 09:51:46 am Michael Haggerty
wrote:
> I can't write more now, but Martin, if you have time to
> benchmark 9944c7faf903a95d4ed9de284ace32debe21cdc1
> against your repository, I would be very interested to
> learn the results.
The fetch no longer seems to suffer from the large
regression, it is now faster (~7m) than 1.7.7 (which was
+15m).
As a quick note, if I comment out the
invalidate_cached_refs() call in write_ref_sha1() on line
2065 (on top of 9944c7), it is still much faster, only ~2m.
Perhaps growing the array on the fly with many refs is still
be too inefficient?
-Martin
--
Employee of Qualcomm Innovation Center, Inc. which is a
member of Code Aurora Forum
prev parent reply other threads:[~2011-10-07 18:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-05 21:29 66 patches and counting Michael Haggerty
2011-10-05 21:36 ` Junio C Hamano
2011-10-05 21:55 ` Jonathan Nieder
2011-10-06 22:16 ` Martin Fick
2011-10-07 1:59 ` Martin Fick
2011-10-07 3:14 ` Michael Haggerty
2011-10-07 15:51 ` Scalable reference handling Michael Haggerty
2011-10-07 18:51 ` Martin Fick [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=201110071251.44052.mfick@codeaurora.org \
--to=mfick@codeaurora.org \
--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).