Git development
 help / color / mirror / Atom feed
From: David Brown <git@davidb.org>
To: git@vger.kernel.org
Subject: Excessive memory consumption.
Date: Mon, 17 Mar 2008 08:43:53 -0700	[thread overview]
Message-ID: <20080317154353.GA9062@old.davidb.org> (raw)

I'm working with a repository containing a large number of revisions (it
has the full 2.6 kernel history) along with a bunch of large tarfiles of
prebuilt images (basically firmware images).  These tarfiles are about 50MB
and are updated frequently.

I'm trying to figure out how to limit memory consumption when fetching from
this repo.  The repo lives on a network drive, and during the

   "remote: Compressing objects: ..."

phase, git-pack-objects quickly grows to 3 or more GB in size.  I've tried
setting  pack.windowMemory = 512m, and pack.deltaCacheLimit = 512m.  Any
other suggested things to try?

This is running 1.5.4.3.

Thanks,
David

             reply	other threads:[~2008-03-17 15:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-17 15:43 David Brown [this message]
2008-03-17 17:04 ` Excessive memory consumption Linus Torvalds

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=20080317154353.GA9062@old.davidb.org \
    --to=git@davidb.org \
    --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