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

Inefficiency of partial shallow clone vs shallow clone + "old-style" sparse checkout

From
KTKonstantin Tokarev <annulen@yandex.ru>
Date
Mar 27, 2020, 21:08 UTC
Message-ID
<2814631585342072@sas8-da6d7485e0c7.qloud-c.yandex.net>
Hello,

Is it a known thing that addition of --filter=blob:none to workflow with shalow clone (e.g. --depth=1) and following sparse checkout may significantly slow down process and result in much larger .git repository?

In case anyone is interested, I've posted my measurements at [1].

I understand this may have something to do with GitHub's server side implementation, but AFAIK there are some GitHub folks here as well.

[1] https://gist.github.com/annulen/835ac561e22bedd7138d13392a7a53be
-- 
Regards,
Konstantin
Next: Jeff King
Message 1 of 13 in “Inefficiency of partial shallow clone vs shallow clone + "old-style" sparse checkout”
  1. Konstantin TokarevMar 27, 2020
  2. Jeff KingMar 28, 2020
  3. Derrick StoleeMar 28, 2020
  4. Taylor BlauMar 31, 2020
  5. Jeff KingApr 1, 2020
  6. Konstantin TokarevMar 31, 2020
  7. Konstantin TokarevMar 31, 2020
  8. Derrick StoleeApr 1, 2020
  9. Konstantin TokarevApr 1, 2020
  10. Jeff KingApr 1, 2020
  11. clone: use "quick" lookup while following tagsJeff King, Apr 1, 2020
  12. Konstantin TokarevApr 1, 2020
  13. Jeff KingApr 1, 2020

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.