git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: worlds slowest git repo- what to do?

From
POPhilip Oakley <philipoakley-7kbabnvhqfm@public.gmane.org>
Date
May 15, 2014, 19:06 UTC
Message-ID
<06A2490FC9BC4461A39B982D3C7C85F7@PhilipOakley>
In-Reply-To
<5374F7C6.5030205@gmail.com>
From: "John Fisher" <fishook2033-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Show 23 quoted lines
>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.
Show 5 quoted lines
>
>
> 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: Sam Vilain
Message 1 of 5 in “Re: worlds slowest git repo- what to do?”
  1. Philip OakleyMay 15, 2014
  2. Sam VilainMay 15, 2014
  3. Duy NguyenMay 16, 2014
  4. John FisherMay 16, 2014
  5. Duy NguyenMay 17, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.