git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicolas Pitre <nico@fluxnic.net>
To: Jeff King <peff@peff.net>
Cc: th.acker66@arcor.de, git@vger.kernel.org
Subject: Re: Large repo and pack.packsizelimit
Date: Tue, 08 May 2012 17:13:13 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.02.1205081709010.21030@xanadu.home> (raw)
In-Reply-To: <20120508203137.GA15707@sigill.intra.peff.net>

On Tue, 8 May 2012, Jeff King wrote:

> On Thu, May 03, 2012 at 01:57:58PM +0200, th.acker66@arcor.de wrote:
> 
> > I am using MSysgit 1.7.9 on WinXP 32bit and have a very large repo
> > (10GB in .git; 20GB in source tree).  I had to set
> > pack.packsizelimit=1024MB to prevent "out of memory" during repacking
> > in git-gc and everything seemed to work fine.
> > 
> > When I tried to clone this repo an "out of memory" occured because the
> > packs to be transferred by the git protocol are not limited by
> > pack.packsizelimit.
> 
> Yes, pack-objects respects pack.packsizelimit when creating local packs,
> but incoming packs from the network (which are processed by index-pack)
> are not split.
> 
> This should be fixed in git. Unfortunately, I don't know that it is as
> trivial as just splitting the incoming stream; we would also have to
> make sure that there were no cross-pack deltas in the result.

IMHO this is the wrong fix.  The pack size limit was created to deal 
with storage media with limited capacity.  In this case, the repack 
process should be told to limit its memory usage, and pack-index should 
simply be taught to cope.


Nicolas

  reply	other threads:[~2012-05-08 21:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-03 11:57 Large repo and pack.packsizelimit th.acker66
2012-05-08 20:31 ` Jeff King
2012-05-08 21:13   ` Nicolas Pitre [this message]
2012-05-08 21:20     ` Jeff King
2012-05-08 21:52       ` Nicolas Pitre
2012-05-09  9:36         ` Thomas
2012-05-09 10:50           ` Nguyen Thai Ngoc Duy
2012-05-09 11:46             ` Thomas
2012-05-09 17:30               ` Junio C Hamano
2012-05-10 11:42                 ` Thomas

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=alpine.LFD.2.02.1205081709010.21030@xanadu.home \
    --to=nico@fluxnic.net \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    --cc=th.acker66@arcor.de \
    /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).