Re: Efficiency of initial clone from server
- From
Jon Smirl <jonsmirl@gmail.com>
- Date
- Feb 11, 2007, 23:25 UTC
- Message-ID
- <9e4733910702111525x176053d3y9fd6d809ac447c0a@mail.gmail.com>
- In-Reply-To
- <20070211225326.GC31488@spearce.org>
On 2/11/07, Shawn O. Pearce <spearce@spearce.org> wrote:
Show 24 quoted lines
> Jon Smirl <jonsmirl@gmail.com> wrote: > > Is this happening because the repository on the server is not > > completely packed? It is basically building a pack of the whole thing > > and shipping it to me, right? > > Correct. The wire protocol only allows us to send one pack. > So we have to pack everything and transmit it as a single unit. > > > If that is the case, why not first pack the whole repository and then > > copy it down the wire? Now the next clone that comes along doesn't > > have to do so much work. Would this help to eliminate some of the load > > at kernel.org? > > Probably, but then the daemon needs write access to the repository. > This isn't required right now; it can be strictly read-only and > still serve the contents. > > > remote: Total 63, written 63 (delta 0), reused 63 (delta 0) > > 100% (63/63) done > > fatal: pack: not a valid SHA1 > > New branch: 0953670fbcb75e26fb93340bddae934e85618f2e > > What version of git is this? That looks like we're assuming the word > pack was an object, but I'm not sure why we would do such a thing...
jonsmirl@jonsmirl:/usr/local/bin$ git --version git version 1.5.0.rc2.g53551-dirty
> > -- > Shawn. >
-- Jon Smirl jonsmirl@gmail.com