From: Jeff King <peff@peff.net>
To: Nicolas Pitre <nico@fluxnic.net>
Cc: th.acker66@arcor.de, git@vger.kernel.org
Subject: Re: Large repo and pack.packsizelimit
Date: Tue, 8 May 2012 17:20:12 -0400 [thread overview]
Message-ID: <20120508212012.GA20044@sigill.intra.peff.net> (raw)
In-Reply-To: <alpine.LFD.2.02.1205081709010.21030@xanadu.home>
On Tue, May 08, 2012 at 05:13:13PM -0400, Nicolas Pitre wrote:
> > 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.
Hmm, you're right. I was thinking it helped to deal with memory
addressing issues for 32-bit systems, but I guess
core.packedGitWindowSize should be handling that. IOW, the 10G packfile
should work just fine for normal access.
However, the OP did say he got an "out of memory" error during the
clone. So maybe there is a problem to be fixed in index-pack there.
-Peff
next prev parent reply other threads:[~2012-05-08 21:20 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
2012-05-08 21:20 ` Jeff King [this message]
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=20120508212012.GA20044@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=nico@fluxnic.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).