From: Adam Heath <doogie@brainfood•com>
To: Sam Hocevar <sam@zoy•org>
Cc: git@vger•kernel.org
Subject: Re: large(25G) repository in git
Date: Tue, 24 Mar 2009 16:44:51 -0500 [thread overview]
Message-ID: <49C95453.9080503@brainfood.com> (raw)
In-Reply-To: <20090324210427.GC30959@zoy.org>
Sam Hocevar wrote:
> As stated several times by Linus and others, Git was not designed
> to handle large files. My stance on the issue is that before trying
> to optimise operations so that they perform well on large files, too,
> Git should usually avoid such operations, especially deltification.
> One notable exception would be someone storing their mailbox in Git,
> where deltification is a major space saver. But usually, these large
> files are binary blobs that do not benefit from delta search (or even
> compression).
Yeah, in this case, I *know* that my binary blobs are completely
different, and it's just a waste of time for git to come to the same
conclusion. I'd be perfectly willing to have some knob I could turn
that would tell git this.
> Since I also need to handle large files (80 GiB repository), I am
> cleaning up some fixes I did, which can be seen in the git-bigfiles
> project (http://caca.zoy.org/wiki/git-bigfiles). I have not yet tried
> to change git-push (because I submit through git-p4), but I hope to
> address it, too. As time goes I believe some of them could make it into
> mainstream Git.
I'd almost be willing to help. I know the basic premise to how git
works, but the devil is in the details, and I don't have time right
now to learn the internals.
Yet another thing to add to my todo list.
> In your particular case, I would suggest setting pack.packSizeLimit
> to something lower. This would reduce the time spent generating a new
> pack file if the problem were to happen again.
Yeah, saw that one, but *after* I had this problem. The default, if
not set, is unlimited, which in this case, is definately *not* what we
want.
next prev parent reply other threads:[~2009-03-24 21:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-23 21:10 large(25G) repository in git Adam Heath
2009-03-24 1:19 ` Nicolas Pitre
2009-03-24 17:59 ` Adam Heath
2009-03-24 18:31 ` Nicolas Pitre
2009-03-24 20:55 ` Adam Heath
2009-03-25 1:21 ` Nicolas Pitre
2009-03-24 18:33 ` david
2009-03-24 8:59 ` Andreas Ericsson
2009-03-24 22:35 ` Adam Heath
2009-03-24 21:04 ` Sam Hocevar
2009-03-24 21:44 ` Adam Heath [this message]
2009-03-25 0:28 ` Nicolas Pitre
2009-03-25 0:57 ` Adam Heath
2009-03-25 1:47 ` Nicolas Pitre
2009-03-26 15:43 ` Marcel M. Cary
2009-03-26 16:35 ` Adam Heath
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=49C95453.9080503@brainfood.com \
--to=doogie@brainfood$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=sam@zoy$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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