From: "Philip Oakley" <philipoakley-7KbaBNvhQFM@public.gmane.org>
To: "John Fisher"
<fishook2033-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
<git-users-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Cc: "Git List" <git-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: worlds slowest git repo- what to do?
Date: Thu, 15 May 2014 20:06:40 +0100 [thread overview]
Message-ID: <06A2490FC9BC4461A39B982D3C7C85F7@PhilipOakley> (raw)
In-Reply-To: 5374F7C6.5030205@gmail.com
From: "John Fisher" <fishook2033-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
>I assert based on one piece of evidence ( a post from a facebook dev)
>that I now have the worlds biggest and slowest git
> repository, and I am not a happy guy. I used to have the worlds
> biggest CVS repository, but CVS can't handle multi-G
> sized files. So I moved the repo to git, because we are using that for
> our new projects.
>
> goal:
> keep 150 G of files (mostly binary) from tiny sized to over 8G in a
> version-control system.
>
> problem:
> git is absurdly slow, think hours, on fast hardware.
>
> question:
> any suggestions beyond these-
> http://git-annex.branchable.com/
> https://github.com/jedbrown/git-fat
> https://github.com/schacon/git-media
> http://code.google.com/p/boar/
> subversion
>
> ?
At the moment some of the developers are looking to speed up some of the
code on very large repos, though I think they are looking at code repos,
rather than large file repos. They were looking for large repos to test
some of the code upon ;-)
I've copied the Git list should they want to make any suggestions.
>
>
> Thanks.
>
> --
Philip
--
You received this message because you are subscribed to the Google Groups "Git for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
For more options, visit https://groups.google.com/d/optout.
next parent reply other threads:[~2014-05-15 19:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5374F7C6.5030205@gmail.com>
2014-05-15 19:06 ` Philip Oakley [this message]
2014-05-15 19:48 ` [git-users] worlds slowest git repo- what to do? Sam Vilain
2014-05-16 10:13 ` Duy Nguyen
[not found] ` <CACsJy8CmiW88tNavRphZa_uMU=jVUCQE6cw5+t2AYnf5dDmcsQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-05-16 21:22 ` John Fisher
2014-05-17 1:49 ` [git-users] " Duy Nguyen
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=06A2490FC9BC4461A39B982D3C7C85F7@PhilipOakley \
--to=philipoakley-7kbabnvhqfm@public.gmane.org \
--cc=fishook2033-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=git-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=git-users-/JYPxA39Uh5TLH3MbocFFw@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox