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

tag storage format

From
UMUri Moszkowicz <uri@4refs.com>
Date
Oct 22, 2012, 22:23 UTC
Message-ID
<CAMJd5ATiAx09eAEo1=6+=hPv=5c6qtOiLRG5jrQn5dfCKUrvMQ@mail.gmail.com>

I'm doing some testing on a large Git repository and am finding local clones to take a very long time. After some investigation I've determined that the problem is due to a very large number of tags (~38k). Even with hard links, it just takes a really long time to visit that many inodes. As it happens, I don't care for most of these tags and will prune many of them anyway but I expect that over time it will creep back up again. Have others reported this problem before and is there a workaround? Perhaps Git should switch to a single-file block text or binary format once a large number of tags becomes present in a repository.

Next: Andreas Schwab
Message 1 of 3 in “tag storage format”
  1. Uri MoszkowiczOct 22, 2012
  2. Andreas SchwabOct 22, 2012
  3. Uri MoszkowiczOct 23, 2012

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.