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

Re: Big project, slow access!

From
Thiago Farina <tfransosi@gmail.com>
Date
Sep 18, 2009, 19:05 UTC
Message-ID
<a4c8a6d00909181205x6b8c348ct270fba6d27df5604@mail.gmail.com>
In-Reply-To
<ffb2c0280909181138r7fde8722n80be4bdf95864c37@mail.gmail.com>
On Fri, Sep 18, 2009 at 3:38 PM, Toan Pham <tpham3783@gmail.com> wrote:
Show 18 quoted lines
> Hi,
>
> I use git to maintain a project that is at least 8 gigs in size.
> The project is a Linux from Scratch repository that includes source
> codes to approximately 2000 open source projects,
> gcc tool-chain, 1000+ configurations for different software packages,
> source code for different kernel versions,
> and many linux distributions/flavors resulted from this LFS build environment.
>
> The git's object repository is now 4.6 gigs and consists of approx.
> 610,000 files and folders.
> The speed of git is now terribly slow.  Each time I use basic commands
> like 'git status' or 'git diff',
> it would take at least 5 minutes for git to give me back a result.
> Again, the machine that i run git on is a P4 3.2 gig-hertz with HT.
>
> would  someone please recommend on how i can optimize git's performance?
> Git is so slow, are there better ways to manage a project like this?

Git is so slow? What you expect with 4.6 gigs? It take some time to do the things. And it is not slow. It is very fast, and it was created with this goal, to be more fast than others VCS.

Show 11 quoted lines
>
>
> Thank you.
>
>
> Toan
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
Previous: Nicolas PitreNext: Nicolas Pitre
Message 3 of 7 in “Big project, slow access!”
  1. Toan PhamSep 18, 2009
  2. Nicolas PitreSep 18, 2009
  3. Thiago FarinaSep 18, 2009
  4. Nicolas PitreSep 18, 2009
  5. R. Tyler BallanceSep 18, 2009
  6. Toan PhamSep 22, 2009
  7. R. Tyler BallanceSep 22, 2009

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.