From: Ping Yin <pkufranky@gmail.com>
To: git mailing list <git@vger.kernel.org>
Subject: What the best git repack option to avoid out of memory (2G free memory)
Date: Sun, 17 Apr 2011 11:24:57 +0800 [thread overview]
Message-ID: <BANLkTimOnuSsSeuZ5QvLQLZBg1QnnDzaNw@mail.gmail.com> (raw)
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"?
And what is the best --window and --window-memory option for the 2G
free available memory?
next reply other threads:[~2011-04-17 3:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-17 3:24 Ping Yin [this message]
2011-04-17 3:32 ` What the best git repack option to avoid out of memory (2G free memory) Ping Yin
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=BANLkTimOnuSsSeuZ5QvLQLZBg1QnnDzaNw@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).