From: Mike Hommey <mh@glandium.org>
Date: Sat, 09 Feb 2008 22:05:51 GMT
Subject: Re: [PATCH] RFC: git lazy clone proof-of-concept
Message-ID: <20080209220551.GA30139@glandium.org>
In-Reply-To: <200802091525.36284.kendy@suse.cz>

On Sat, Feb 09, 2008 at 03:25:35PM +0100, Jan Holesovsky wrote:
> Hi Nicolas,
> 
> On Friday 08 February 2008 19:03, Nicolas Pitre wrote:
> 
> > > I've provided a git import of OOo with the entire history; the problem is
> > > that the pack has 2.5G, so it's not too convenient to download for casual
> > > developers that just want to try it.
> >
> > How did you repack your repository?
> >
> > We know that current defaults are not suitable for large projects.  For
> > example, the gcc git repository shrinked from 1.5GB pack down to 230MB
> > after some tuning.
> 
> After the suggestions in this thread I tried to experiment with the --window 
> and --depth options of git-repack, and indeed, there are still reserves.
> 
> So far I'm at 2G (saved 500M), unfortunately the aggressive values like 
> --window=250 --depth=250 that someone mentioned here cause out-of-memory on a 
> machine with 8G :-(. If there's anybody brave enough here to try as well, I'd 
> be grateful.  Maybe it would be also interesting to _exactly_ locate what 
> causes the oom, and eg. exclude the object from the pack if possible.

Speaking of which, I haven't taken a look at builtin-pack-objects.c deep
enough but shouldn't it be possible to do prepare_pack and
write_pack_file in one pass ?

Mike