git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Fisher <fishook2033-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Duy Nguyen <pclouds-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	John Fisher <fishook2033-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: git-users-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org,
	Git List <git-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	 Philip Oakley <philipoakley-7KbaBNvhQFM@public.gmane.org>
Subject: Re: worlds slowest git repo- what to do?
Date: Fri, 16 May 2014 14:22:44 -0700	[thread overview]
Message-ID: <537681A4.2070601@gmail.com> (raw)
In-Reply-To: <CACsJy8CmiW88tNavRphZa_uMU=jVUCQE6cw5+t2AYnf5dDmcsQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>


On 05/16/2014 03:13 AM, Duy Nguyen wrote:
> On Fri, May 16, 2014 at 2:06 AM, Philip Oakley <philipoakley-7KbaBNvhQFM@public.gmane.org> wrote:
>> 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.
> I think your best bet so far is git-annex 

good, I am  looking at that

> (or maybe bup) for dealing
> with huge files. I plan on resurrecting Junio's split-blob series to
> make core git handle huge files better, but there's no eta on that.
> The problem here is about file size, not the number of files, or
> history depth, right?

When things here calm down, I could easily test the repo without the giant files, leaving 99% of files in the repo.
There is hardly any history depth because these are releases, version controlled by directory name. As has been
suggested I could be forced to abandon the version-control, even to the point of just using rsync.  But I've been doing
this with CVS for 10 years now and I hate to change or in any way move away fron KISS. Moving it to Git may not have
been one of my better ideas...


> Probably known issues. But some elaboration would be nice (e.g. what operation is slow, how slow, some more detail
> characteristics of the repo..) in case new problems pop up. 

so far I have done add, commit, status, clone - commit and status are slow; add seems to depend on the files involved,
clone seems to run at network speed.
I can provide metrics later, see above. email me offline with what you want.

John

-- 
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.

  parent reply	other threads:[~2014-05-16 21:22 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 ` worlds slowest git repo- what to do? Philip Oakley
2014-05-15 19:48   ` [git-users] " 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 [this message]
2014-05-17  1:49         ` 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=537681A4.2070601@gmail.com \
    --to=fishook2033-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=git-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=git-users-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
    --cc=pclouds-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=philipoakley-7KbaBNvhQFM@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;
as well as URLs for NNTP newsgroup(s).