git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: Nicolas Pitre <nico@cam.org>
Cc: Jon Smirl <jonsmirl@gmail.com>,
	"Shawn O. Pearce" <spearce@spearce.org>,
	Junio C Hamano <junkio@cox.net>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: Efficiency of initial clone from server
Date: Mon, 12 Feb 2007 14:35:07 -0500	[thread overview]
Message-ID: <20070212193507.GA18730@thunk.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0702121013150.1757@xanadu.home>

On Mon, Feb 12, 2007 at 10:20:31AM -0500, Nicolas Pitre wrote:
> Repacking on clone is not the solution at all.
> 
> This problem is going to largely be resolved when GIT 1.5.0 gets 
> installed on kernel.org.  With latest GIT, pushes are kept as packs on 
> the remote end (when they're big enough which is over 100 objects by 
> default).  Then repacking multiple packs into one is almost free as most 
> of the data is simply copied from one pack and sent over the wire as a 
> single pack.

Even before we get Git 1.5.0 installed on master.kernel.org (and we
should really ask hpa to do that), is there a reason we haven't done
something like this across all of the kernel repo's on
master.kernel.org?

for i in <list of kernel git repo's on master.kernel.org>
do
   pushd $i
   if [ ! -f objects/info/alternates ]; then
	echo /pub/scm/linux/kernel/git/torvalds/linux-2.6.git/objects \
	   > objects/info/alternates
	git repack -a -d -l
   fi
   popd
done


					- Ted

  reply	other threads:[~2007-02-12 19:35 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 [this message]
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

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=20070212193507.GA18730@thunk.org \
    --to=tytso@mit.edu \
    --cc=git@vger.kernel.org \
    --cc=jonsmirl@gmail.com \
    --cc=junkio@cox.net \
    --cc=nico@cam.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).