Re: Git exhausts memory.
- From
- Alif Wahid <alif.wahid@gmail.com>
- Date
- Apr 5, 2011, 11:26 UTC
- Message-ID
- <BANLkTi=cBcsu1uehkLUP8-io9r1j-=jmNg@mail.gmail.com>
- In-Reply-To
- <BANLkTi=nzY7wFTr3647SYkSMHx=AityRgw@mail.gmail.com>
On 5 April 2011 21:13, Nguyen Thai Ngoc Duy <pclouds@gmail.com> wrote:
Show 17 quoted lines
> On Tue, Apr 5, 2011 at 11:35 AM, Alif Wahid <alif.wahid@gmail.com> wrote: >> It seems to me that if "git init" creates a $GIT_DIR/info/attributes >> file by default with a line like "*.gz -delta", then that will disable >> the memory intensive deltra compression plumbing for those special >> cases where people need to track gzip archives (similarly another line >> "*.bz2 -delta" for bzip2 archives and so on). Since these files can't >> supposedly be compressed much more, I think Git ought to have a >> default heuristic to not attempt any compression on them. > > I was thinking of very similar thing on my ride home. But I selected > files on size, not extension. With the (hopefully coming soon) > introduction of pathspec magic specifier [1], we can teach git-attr to > express "files that have size in a range [a,b]" (either a or b can be > infinite). The rest is like yours: applying -delta on selected files > then put such a rule with a default range in default template. > > [1] http://thread.gmane.org/gmane.comp.version-control.git/169813/focus=169844
Yeah, makes sense.
I also noticed the following thread regarding big file support. Most of the details there are related to this issue as well.
http://thread.gmane.org/gmane.comp.version-control.git/170649/focus=170649
Alif