Tim Allen [off-list ref] 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.