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

Re: Any tips for improving the performance of cloning large repositories?

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 16, 2011, 17:08 UTC
Message-ID
<7vzkesigw9.fsf@alter.siamese.dyndns.org>
In-Reply-To
<CAJ-05NPbRmyx=a+U7BK4rNShBgaXj+g-Bwc1aBDDb3N0VPBW=A@mail.gmail.com>
Alex Bennee <kernel-hacker@bennee.com> writes:
> Well that's counter intuitive....
>
>  - reverting the original repo to one big pack speeds up the clone
>  - adding a --local --reference mirror slows it down

Neither is. Read what "--local" says in the help text of clone. It disables the git aware clever optimization.

Previous: Alex BenneeNext: Alex Bennee
Message 6 of 7 in “Any tips for improving the performance of cloning large repositories?”
  1. Alex BenneeDec 16, 2011
  2. Hallvard Breien FurusethDec 16, 2011
  3. Hallvard Breien FurusethDec 16, 2011
  4. Seth RobertsonDec 16, 2011
  5. Alex BenneeDec 16, 2011
  6. Junio C HamanoDec 16, 2011
  7. Alex BenneeDec 16, 2011

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.