All of lore.kernel.org
 help / color / mirror / Atom feed
From: th.acker66@arcor.de
To: git@vger.kernel.org
Subject: Large repo and pack.packsizelimit
Date: Thu, 3 May 2012 13:57:58 +0200 (CEST)	[thread overview]
Message-ID: <37267143.413194.1336046278583.JavaMail.ngmail@webmail07.arcor-online.net> (raw)

Hello,

I am using MSysgit 1.7.9 on WinXP 32bit and have a very large repo (10GB in .git; 20GB in source tree).
I had to set pack.packsizelimit=1024MB to prevent "out of memory" during repacking in git-gc 
and everything seemed to work fine.

When I tried to clone this repo an "out of memory" occured because the packs to be transferred
by the git protocol are not limited by pack.packsizelimit. I "fixed" this by setting transfer.unpackLimit=100000
and thus transferring only loose objects. This is very slow but it works.

In this cloned repo now git-gc again causes "out of memory" because it tries to pack all loose
objects in one go thereby seemingly not respecting pack.packsizelimit ... 
(Setting --window-memory=512m in git-repack did not help here.)

Am I doing anything wrong here or is this a bug/feature in git?

BTW1 Repo is very large but contains only one really large file with 1.2GB; all other files are smaller than 256MB.
BTW2 I cannot use 1.7.10 due to the http authorization bug.


---
Thomas

             reply	other threads:[~2012-05-03 11:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-03 11:57 th.acker66 [this message]
2012-05-08 20:31 ` Large repo and pack.packsizelimit Jeff King
2012-05-08 21:13   ` Nicolas Pitre
2012-05-08 21:20     ` Jeff King
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=37267143.413194.1336046278583.JavaMail.ngmail@webmail07.arcor-online.net \
    --to=th.acker66@arcor.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.