git and larger trees, not so fast?

Previous thread: git and larger trees, not so fast? by moe on Thursday, August 9, 2007 - 12:30 pm. (36 messages)

Next thread: Re: git and larger trees, not so fast? by David Kastrup on Thursday, August 9, 2007 - 2:06 pm. (1 message)
To: <git@...>
Date: Thursday, August 9, 2007 - 12:06 pm

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

-

Previous thread: git and larger trees, not so fast? by moe on Thursday, August 9, 2007 - 12:30 pm. (36 messages)

Next thread: Re: git and larger trees, not so fast? by David Kastrup on Thursday, August 9, 2007 - 2:06 pm. (1 message)