From: Seth Robertson <in-gitvger@baka.org>
Date: Fri, 16 Dec 2011 14:14:59 GMT
Subject: Re: Any tips for improving the performance of cloning large repositories?
Message-ID: <201112161414.pBGEExLJ006769@no.baka.org>
In-Reply-To: <hbf.20111216zcin@bombur.uio.no>


In message <hbf.20111216zcin@bombur.uio.no>, Hallvard Breien Furuseth writes:

    I wrote:
    > Do you often need to clone from a remote?  Instead of cloning from a
    > local (git clone --mirror) which gets auto-updated from the remote.

    Er, obviously not, since you tried that with rsync.  Create the mirror
    with 'git clone --mirror', then update it with 'git fetch' rather than
    rsync.

If you really need to perform a full clone from the buildbot with or
without a different working directory (for instance if you have
buildbots/checkout users running in parallel where multiple users need
a consistent HEAD for multiple sequential operations) then instead
consider cloning with --reference or --shared.  There are severe
restrictions on what you should do with aggressive sharing (man
git-clone), but if all you are doing is normal checkouts, tags,
commits, etc, then it would be just fine.  Of course remember to add a
remote for the real upstream if you are planning on pushing
changes/tags back.

					-Seth Robertson