From: Junio C Hamano <gitster@pobox.com>
To: Johan Herland <johan@herland.net>
Cc: Daniel Barkalow <barkalow@iabervon.org>, git@vger.kernel.org
Subject: Re: [RFC/PATCH 0/3] Teach builtin-clone to pack refs
Date: Sat, 22 Mar 2008 17:45:56 -0700 [thread overview]
Message-ID: <7v8x0agtdn.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <200803220210.30957.johan@herland.net> (Johan Herland's message of "Sat, 22 Mar 2008 02:10:30 +0100")
Johan Herland <johan@herland.net> writes:
> Although most of the speedup from current "next" is achieved by the
> builtin-clone work, there is still a considerable additional improvement
> from writing all refs to a single file instead of writing one file per
> ref. I expect the performance improvement to be much bigger on platforms
> with slower filesystem (aka. Windows).
At some point, additional speedups are hidden in the noise.
Not writing reflogs is a _different_ behaviour from the previous, but I
suspect it might even be an improvement. When you have 1000 remote
branches, probably most of them are not even active.
next prev parent reply other threads:[~2008-03-23 0:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-22 1:10 [RFC/PATCH 0/3] Teach builtin-clone to pack refs Johan Herland
2008-03-22 1:12 ` [RFC/PATCH 1/3] Move pack_refs() and friends into libgit Johan Herland
2008-03-22 1:13 ` [RFC/PATCH 2/3] Prepare testsuite for a "git clone" that packs refs Johan Herland
2008-04-14 6:10 ` Daniel Barkalow
2008-04-14 8:00 ` Johan Herland
2008-04-14 8:02 ` [PATCH 1/4] Incorporate fetched packs in future object traversal Johan Herland
2008-04-14 8:02 ` [PATCH 2/4] Move pack_refs() and friends into libgit Johan Herland
2008-04-14 8:03 ` [PATCH 3/4] Prepare testsuite for a "git clone" that packs refs Johan Herland
2008-04-14 8:04 ` [PATCH 4/4] Teach "git clone" to pack refs Johan Herland
2008-03-22 1:13 ` [PATCH 3/3] " Johan Herland
2008-03-22 1:31 ` Daniel Barkalow
2008-03-23 0:45 ` Junio C Hamano [this message]
2008-03-23 9:49 ` [RFC/PATCH 0/3] Teach builtin-clone " Johan Herland
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=7v8x0agtdn.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=johan@herland.net \
/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).