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

[Question] clone performance

From
Rrandall.s.becker@rogers.com <randall.s.becker@rogers.com>
Date
Aug 24, 2019, 01:59 UTC
Message-ID
<005f01d55a1f$88e2ab20$9aa80160$@rogers.com>
Hi All,

I'm trying to answer a question for a customer on clone performance. They are doing at least 2-3 clones a day, of repositories with about 2500 files and 10Gb of content. This is stressing the file system. I have tried to convince them that their process is not reasonable and should stick with existing clones, using branch checkout rather that re=cloning for each feature branch. Sadly, I have not been successful - not for a lack of trying. Is there any way to improve raw clone performance in a situation like this, where status really doesn't matter, because the clone's life span is under 48 hours.

TIA, Randall

Next: Bryan Turner
Message 1 of 5 in “[Question] clone performance”
  1. randall.s.becker@rogers.comAug 24, 2019
  2. Bryan TurnerAug 24, 2019
  3. randall.s.becker@rogers.comAug 26, 2019
  4. Jeff KingAug 26, 2019
  5. Elijah NewrenAug 26, 2019

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.