From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: "Git Mailing List" <git@vger.kernel.org>
Subject: Re: Efficiency of initial clone from server
Date: Sun, 11 Feb 2007 18:29:00 -0500 [thread overview]
Message-ID: <9e4733910702111529g715c7c0ch9246947fd70d40eb@mail.gmail.com> (raw)
In-Reply-To: <20070211225326.GC31488@spearce.org>
On 2/11/07, Shawn O. Pearce <spearce@spearce.org> wrote:
> 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.
Does it need write access for push to work, can the server check for
write access and save the complete repack if it has access? This
appears to be causing a lot of needless work for kernel.org.
--
Jon Smirl
jonsmirl@gmail.com
prev parent reply other threads:[~2007-02-11 23:29 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-11 19:53 Efficiency of initial clone from server Jon Smirl
2007-02-11 22:53 ` Shawn O. Pearce
2007-02-11 23:25 ` Jon Smirl
2007-02-11 23:51 ` Jon Smirl
2007-02-12 1:38 ` Nicolas Pitre
2007-02-12 2:15 ` Jon Smirl
2007-02-12 3:55 ` Nicolas Pitre
2007-02-12 4:49 ` Shawn O. Pearce
2007-02-12 16:42 ` Nicolas Pitre
2007-02-12 4:16 ` Junio C Hamano
2007-02-12 4:29 ` Jon Smirl
2007-02-12 4:33 ` Junio C Hamano
2007-02-12 4:53 ` Jon Smirl
2007-02-12 5:01 ` Jon Smirl
2007-02-12 5:11 ` Shawn O. Pearce
2007-02-12 5:17 ` Jon Smirl
2007-02-12 15:20 ` Nicolas Pitre
2007-02-12 19:35 ` Theodore Tso
2007-02-12 20:53 ` Junio C Hamano
2007-02-12 21:33 ` Nicolas Pitre
2007-02-13 0:51 ` Jakub Narebski
2007-02-12 5:30 ` Junio C Hamano
2007-02-12 5:55 ` Jon Smirl
2007-02-12 6:08 ` Junio C Hamano
2007-02-12 15:24 ` Jon Smirl
2007-02-12 16:40 ` Jon Smirl
2007-02-12 17:04 ` Shawn O. Pearce
2007-02-12 11:45 ` Johannes Schindelin
2007-02-12 14:31 ` Jon Smirl
2007-02-12 17:06 ` Shawn O. Pearce
2007-02-13 15:03 ` Andreas Ericsson
2007-02-11 23:29 ` Jon Smirl [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9e4733910702111529g715c7c0ch9246947fd70d40eb@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).