From: Ping Yin <pkufranky@gmail.com>
To: git mailing list <git@vger.kernel.org>
Subject: Re: What the best git repack option to avoid out of memory (2G free memory)
Date: Sun, 17 Apr 2011 11:32:44 +0800 [thread overview]
Message-ID: <BANLkTi=ABGrsUCxpB6fUXCP0477iq=irhw@mail.gmail.com> (raw)
In-Reply-To: <BANLkTimOnuSsSeuZ5QvLQLZBg1QnnDzaNw@mail.gmail.com>
On Sun, Apr 17, 2011 at 11:24 AM, Ping Yin <pkufranky@gmail.com> wrote:
> When "gc --auto --aggressive --prune" android platform/prebuilt.git, i
> encountered the following error:
>
> Auto packing the repository for optimum performance.
> warning: suboptimal pack - out of memory
> fatal: Out of memory, malloc failed
> error: failed to run repack
>
> I have 2G free memory available and found the --window and
> --window-memory option in git repack. However, i wonder how to compute
> the max memory git-repack will use, is it "window * window-memory"?
>
Or "window * windowMemory * threads"?
prev parent reply other threads:[~2011-04-17 3:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-17 3:24 What the best git repack option to avoid out of memory (2G free memory) Ping Yin
2011-04-17 3:32 ` Ping Yin [this message]
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='BANLkTi=ABGrsUCxpB6fUXCP0477iq=irhw@mail.gmail.com' \
--to=pkufranky@gmail.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).