From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
To: Nicolas Pitre <nico@fluxnic.net>, Git Mailing List <git@vger.kernel.org>
Cc: Alif Wahid <alif.wahid@gmail.com>
Subject: Re: Git exhausts memory.
Date: Mon, 4 Apr 2011 21:57:01 +0700 [thread overview]
Message-ID: <BANLkTinU7x16yp+y-HW9UhkVn9SftOJCcA@mail.gmail.com> (raw)
In-Reply-To: <BANLkTinCwZG3+0Ss8o9ODptg=L8LKKN7aQ@mail.gmail.com>
On Mon, Apr 4, 2011 at 7:52 PM, Alif Wahid <alif.wahid@gmail.com> wrote:
> Hi Nicolas,
>
> On 4 April 2011 01:18, Nicolas Pitre <nico@fluxnic.net> wrote:
>>
>> Something you can try is to simply tell Git not to attempt any delta
>> compression on those tar files using gitattributes (see the man page of
>> the same name).
Should we change the default to not delta if a blob exceeds predefined
limit (say 128M)? People who deliberately wants to delta them can
still set delta attr. 1.8.0 material maybe?
> Seems to have worked. Both git-gc and git-repack appear to be less
> memory hungry now and do actually run to completion without failure.
>
> Thanks for your help.
--
Duy
next prev parent reply other threads:[~2011-04-04 14:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-02 5:01 Git exhausts memory Alif Wahid
2011-04-02 15:05 ` Nicolas Pitre
2011-04-03 9:15 ` Alif Wahid
2011-04-03 15:18 ` Nicolas Pitre
2011-04-04 12:52 ` Alif Wahid
2011-04-04 14:57 ` Nguyen Thai Ngoc Duy [this message]
2011-04-05 2:22 ` David Fries
2011-04-05 4:35 ` Alif Wahid
2011-04-05 11:13 ` Nguyen Thai Ngoc Duy
2011-04-05 11:26 ` Alif Wahid
2011-04-05 16:48 ` Holger Hellmuth
2011-04-05 17:06 ` Shawn Pearce
2011-04-05 17:44 ` Junio C Hamano
2011-04-05 20:56 ` Nicolas Pitre
2011-04-05 22:16 ` Junio C Hamano
2011-04-05 22:19 ` Shawn Pearce
2011-04-06 0:34 ` Nicolas Pitre
2011-04-06 15:51 ` Jay Soffian
2011-04-06 16:33 ` Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BANLkTinU7x16yp+y-HW9UhkVn9SftOJCcA@mail.gmail.com \
--to=pclouds@gmail.com \
--cc=alif.wahid@gmail.com \
--cc=git@vger.kernel.org \
--cc=nico@fluxnic.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).