From: Shawn Pearce <spearce@spearce.org>
To: Kartik Agaram <ak@akkartik.com>
Cc: git@vger.kernel.org
Subject: Re: how to keep git-fetch from running out of memory?
Date: Sun, 15 May 2011 12:13:55 -0700 [thread overview]
Message-ID: <BANLkTinRkePRMQzQS7k=3bSTxTJRVpG39Q@mail.gmail.com> (raw)
In-Reply-To: <BANLkTinnOTr+PUzBMpx1DLcxs8CVWjy33A@mail.gmail.com>
On Sat, May 14, 2011 at 22:24, Kartik Agaram <ak@akkartik.com> wrote:
> I have a git repo with some large files that I'm no longer able to
> update. git fetch keeps running out of memory:
>
> fatal: Out of memory, malloc failed
> fatal: unpack-objects died with error code 128
>
> Anybody know how to keep it from compressing the refs into packfiles?
> I've experimented with core.compression, pack.compression,
> pack.windowMemory, pack.packSizeLimit, all without luck :(
Instead of playing with these settings, try transfer.unpackLimit 1. It
will force the code to use index-pack rather than unpack-objects,
which has a different memory profile.
However, that may still be insufficient. A big object must still be
allocated in memory in order to compute its SHA-1. If you don't have
sufficient memory, you need to increase your ulimits, or reconfigure
your system to have more virtual memory available to the process.
--
Shawn.
next prev parent reply other threads:[~2011-05-15 19:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-15 5:24 how to keep git-fetch from running out of memory? Kartik Agaram
2011-05-15 19:13 ` Shawn Pearce [this message]
2011-05-15 20:25 ` Junio C Hamano
2011-05-15 20:37 ` Shawn Pearce
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='BANLkTinRkePRMQzQS7k=3bSTxTJRVpG39Q@mail.gmail.com' \
--to=spearce@spearce.org \
--cc=ak@akkartik.com \
--cc=git@vger.kernel.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).