Re: Efficiency of initial clone from server

From: Junio C Hamano <junkio@cox.net>
Date: Feb 12, 2007, 05:30 UTC
Message-ID: <7vzm7k9c3c.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <9e4733910702112101h256b1468j5de65c6e89109a22@mail.gmail.com>

"Jon Smirl" <jonsmirl@gmail.com> writes:

Show 16 quoted lines

> On 2/11/07, Jon Smirl <jonsmirl@gmail.com> wrote:
>> Same thing with cg clone, it's what is broken.
>> cg update is broken in the same way.
>> I'm using the current git version of cogitio.
>> I'll switch to the git commands, git clone is about 10x faster for the
>> clone anyway.
>
> Don't read anything into the 10x speed diff, my last git clone was
> really slow. I'm probably fighting other people at kernel.org to keep
> the tree in RAM.
>
> But pack to the original point, can't the server check and see if it
> has write access so that it can keep the fully packed tree? I've just
> caused kernel.org to needlessly repack the wireless-dev tree a dozen
> times playing with this clone command. If it didn't have to keep
> repacking for the clone, clone would be a lot faster.

You are assuming everybody does initial clone all the time. I do not think that holds true in practice.

For something like tglx historical tree that will _never_ change, there is a specific hack the repository owner can take advantage of to always feed a prepackaged pack, although its use is not advertised well enough (and I do not think it buys much in practice).