From: Tay Ray Chuan <rctay89@gmail.com>
To: "Wilson, Kevin Lee (OpenView Engineer)" <kevin.l.wilson@hp.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: GIT as binary repository
Date: Thu, 21 Oct 2010 22:19:51 +0800 [thread overview]
Message-ID: <AANLkTim6qsUDf5LS7C9o+C92Aqh7CohLLJ=+13BE3Tze@mail.gmail.com> (raw)
In-Reply-To: <2EBB46ACFCD6CF48B45E2B1865BD02338037D36B4E@GVW1098EXB.americas.hpqcorp.net>
Hi,
On Thu, Oct 21, 2010 at 8:52 PM, Wilson, Kevin Lee (OpenView Engineer)
<kevin.l.wilson@hp.com> wrote:
> We are investigating the use of GIT as a binary repository solution. Our larger files are near 800MB and the total checked out repo size is about 3 GB the repo size in SVN is more like 20-30GB, if we could prune the history prior to MR, we could get these sizes down considerably. This binary repo is really for our super project build. From what I have read and learned, this is not a good fit for the GIT tool. Have there been performance improvements lately? Some of the posts I have read have been quite old?
check this out:
http://github.com/apenwarr/bup
It's a modified git system that's purpose-built for large files.
That's just about all the sensible information I can share you with
you.
--
Cheers,
Ray Chuan
next prev parent reply other threads:[~2010-10-21 14:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-21 12:52 GIT as binary repository Wilson, Kevin Lee (OpenView Engineer)
2010-10-21 14:19 ` Tay Ray Chuan [this message]
2010-10-21 19:54 ` Enrico Weigelt
2010-10-21 21:23 ` Shawn Pearce
2010-10-22 5:02 ` Enrico Weigelt
2010-10-22 19:20 ` Shawn Pearce
2010-10-21 17:38 ` Shawn Pearce
2010-10-21 18:53 ` Wilson, Kevin Lee (OpenView Engineer)
2010-10-21 19:19 ` Enrico Weigelt
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='AANLkTim6qsUDf5LS7C9o+C92Aqh7CohLLJ=+13BE3Tze@mail.gmail.com' \
--to=rctay89@gmail.com \
--cc=git@vger.kernel.org \
--cc=kevin.l.wilson@hp.com \
/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;
as well as URLs for NNTP newsgroup(s).