git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: moe <moe-git@mbox.bz>
To: git@vger.kernel.org
Subject: git and larger trees, not so fast?
Date: Thu, 9 Aug 2007 18:06:56 +0200	[thread overview]
Message-ID: <20070809160655.GA19494@mbox.bz> (raw)

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

             reply	other threads:[~2007-08-09 16:40 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-09 16:06 moe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-08-09 16:30 git and larger trees, not so fast? moe
2007-08-09 17:11 ` Linus Torvalds
2007-08-09 17:38   ` Linus Torvalds
2007-08-09 18:00     ` Junio C Hamano
2007-08-09 18:06     ` Linus Torvalds
2007-08-09 18:11       ` Junio C Hamano
2007-08-09 20:42         ` Junio C Hamano
2007-08-09 20:52           ` Sean
2007-08-09 21:37             ` Junio C Hamano
2007-08-09 21:41             ` Linus Torvalds
2007-08-09 21:46               ` Linus Torvalds
2007-08-09 22:02                 ` Junio C Hamano
2007-08-09 23:38                   ` Junio C Hamano
2007-08-10  0:04                     ` Junio C Hamano
2007-08-10  0:44                     ` Linus Torvalds
2007-08-10  0:51                       ` Junio C Hamano
2007-08-10  0:57                         ` Linus Torvalds
2007-08-10  3:48                           ` Junio C Hamano
2007-08-10  5:55                             ` Junio C Hamano
2007-08-10 15:49                               ` Linus Torvalds
2007-08-10 16:07                             ` Linus Torvalds
2007-08-10  1:42                   ` Daniel Barkalow
2007-08-09 17:54   ` Linus Torvalds
2007-08-09 18:06   ` David Kastrup
2007-08-10 19:39 ` Linus Torvalds
2007-08-11 18:47 ` Linus Torvalds
2007-08-11 19:02   ` Fernando J. Pereda
2007-08-11 20:38     ` Linus Torvalds
2007-08-11 20:51       ` Fernando J. Pereda
2007-08-11 22:27         ` Linus Torvalds
2007-08-11 23:26           ` David Kastrup
2007-08-11 20:06   ` moe
2007-08-23  0:30     ` moe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070809160655.GA19494@mbox.bz \
    --to=moe-git@mbox.bz \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).