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

git and larger trees, not so fast?

From
Mmoe <moe-git@mbox.bz>
Date
Aug 9, 2007, 16:06 UTC
Message-ID
<20070809160655.GA19494@mbox.bz>
hi guys,

earlier today i imported one of my larger trees (~70k files) into git and was quite disappointed by the performance.

i made some tests on latest master branch (1.5.3.rc4.29.g74276) and it seems like git hits a wall somewhere above ~50k files.

i'm seeing 'commit' timings of 30s and up as well as 'status' timings in the 10s ballpark.

here's a test-case (should be safe to copy/paste on linux, bash):

# # first create a tree of roughly 100k files # mkdir bummer cd bummer for ((i=0;i<100;i++)); do mkdir $i && pushd $i; for ((j=0;j<1000;j++)); do echo "$j" >$j; done; popd; done

# # init and add this to git # time git init git config user.email "no@thx" git config user.name "nothx" time git add . time git commit -m 'buurrrrn' -a

# # git-status, tunes in at around ~10s for me # time git-status time git-status time git-status

# # git-commit, takes a whopping 52s for me # date >50/500 time git commit -m 'expose the turtle' 50/500

regards, moe

Message 1 of 1 in “git and larger trees, not so fast?”
  1. moeAug 9, 2007

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.