From: Junio C Hamano <junkio@cox.net>
To: Tim Allen <tim@commsecure.com.au>
Cc: git@vger.kernel.org
Subject: Re: Git performance problems with many tags
Date: Sun, 25 Mar 2007 23:13:07 -0700 [thread overview]
Message-ID: <7vwt14zg5o.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20070326045341.GE10545@ws35.commsecure.com.au> (Tim Allen's message of "Mon, 26 Mar 2007 14:53:41 +1000")
Tim Allen <tim@commsecure.com.au> writes:
> However, operations like 'git-fetch' take much, much longer in our
> repository than in the kernel repository: a git-fetch that pulls no
> updates in the kernel repository takes 1.7s, while our repository
> (fetching from one repository to a clone on the same local disk) takes
> about 20 seconds.
> ...
> Does git have known scalability problems with large numbers of tags? Is
> there anything we can do to mitigate this slowdown, apart from just not
> using git's tag feature at all? Are there any details I've overlooked or
> misunderstood?
An optimization for "fetching between repositories with insane
number of refs" problem was merged after v1.5.0, so if you try
the current tip of 'master' (which happens to be at v1.5.1-rc2
right now), I suspect you may see significant improvements.
prev parent reply other threads:[~2007-03-26 6:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-26 4:53 Git performance problems with many tags Tim Allen
2007-03-26 6:07 ` Shawn O. Pearce
2007-03-26 6:13 ` Junio C Hamano [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=7vwt14zg5o.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=tim@commsecure.com.au \
/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