Re: [PATCH] RFC: git lazy clone proof-of-concept

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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.

The tree is available here:

git clone git://o3-build.services.openoffice.org/git/ooo.git
git clone http://o3-build.services.openoffice.org/~svn/ooo.git (the same over 
http://)

Thank you in advance!

Regards,
Jan
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux