Re: [RFC/PATCH 0/3] Teach builtin-clone to pack refs
On Sunday 23 March 2008, Junio C Hamano wrote:
Show 9 quoted lines
> 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.
Yes, however, I bet you'll notice the difference between writing 11000 files on Windows, and writing 1.
Unfortunately, this scenario is not as far fetched as some may think: At $dayjob I'm working on converting old CVS modules with up to ~10 years of history, and some of the resulting repos have ~30000 refs (mostly build tags). Although I'll probably remove the build tags before preparing the repos that most other developers will see, I'll still have to keep the build tags around somewhere, in case devs need to refer to them. And, of course, most devs are still Windows-users. Keeping refs packed is pretty much crucial in this scenario.
> 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.
Exactly my thinking as well. And for those few that _are_ active, you'll still of course get regular reflog entries when they _do_ change.
...Johan
--
Johan Herland, <johan@herland.net>
www.herland.net
Johan Herland <johan@herland.net>