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

Performance impact of a large number of commits

From
SASamuel Abels <newsgroups@debain.org>
Date
Oct 24, 2008, 19:02 UTC
Message-ID
<1224874946.7566.13.camel@localhost>
Hi,

I am considering Git to maintain a repository of approximately 300.000 files totaling 1 GB, with a number of ~100.000 commits per day, all in one single branch. The only operations performed are "git commit", "git show", and "git checkout", and all on one local machine. Does this sound like a reasonable thing to do with Git?

-Samuel
Next: david@lang.hm
Message 1 of 7 in “Performance impact of a large number of commits”
  1. Samuel AbelsOct 24, 2008
  2. david@lang.hmOct 24, 2008
  3. Samuel AbelsOct 24, 2008
  4. david@lang.hmOct 24, 2008
  5. Samuel AbelsOct 25, 2008
  6. david@lang.hmOct 25, 2008
  7. Samuel AbelsOct 25, 2008

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.