From: Jakub Narebski <jnareb@gmail.com>
To: "Edward Ned Harvey" <git@nedharvey.com>
Cc: <git@vger.kernel.org>
Subject: Re: git performance
Date: Wed, 22 Oct 2008 15:42:51 -0700 (PDT) [thread overview]
Message-ID: <m3d4hsi708.fsf@localhost.localdomain> (raw)
In-Reply-To: <000801c93483$2fdad340$8f9079c0$@com>
"Edward Ned Harvey" <git@nedharvey.com> writes:
> I see things all over the Internet saying git is fast. I'm
> currently struggling with poor svn performance and poor attitude of
> svn developers, so I'd like to consider switching to git. A quick
> question first.
>
> The core of the performance problem I'm facing is the need to "walk
> the tree" for many thousand files. Every time I do "svn update" or
> "svn status" the svn client must stat every file to check for local
> modifications (a coffee cup or a beer worth of stats). In essence,
> this is unavoidable if there is no mechanism to constantly monitor
> filesystem activity during normal operations. Analogous to
> filesystem journaling.
>
> So - I didn't see anything out there saying "git is fast because it
> uses inotify" or anything like that. Perhaps git would not help me
> at all? Because git still needs to stat all the files in the tree?
http://git.or.cz/gitwiki/GitBenchmarks
While it should be possible to use 'assume unchanged' bit together
with inotify / icron, it is not something tha is done; IIRC Mercurial
had Linux-only InotifyPlugin...
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2008-10-22 22:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-22 20:17 git performance Edward Ned Harvey
2008-10-22 20:36 ` Jeff King
2008-10-22 21:13 ` Peter Harris
2008-10-22 21:55 ` Edward Ned Harvey
2008-10-23 7:11 ` Andreas Ericsson
2008-10-23 7:11 ` Andreas Ericsson
2008-10-23 7:41 ` Andreas Ericsson
2008-10-23 12:16 ` Matthieu Moy
2008-10-23 16:39 ` Jeff King
[not found] ` <000001c9358f$232bac70$69830550$@com>
2008-10-24 14:29 ` Jeff King
2008-10-24 17:42 ` George Shammas
2008-10-24 19:06 ` Jakub Narebski
2008-10-24 17:53 ` Linus Torvalds
2008-10-24 18:20 ` Jeff King
2008-10-23 18:31 ` Daniel Barkalow
2008-10-23 22:24 ` Nanako Shiraishi
2008-10-24 3:56 ` Daniel Barkalow
2008-10-24 7:55 ` Pete Harlan
2008-10-24 23:10 ` Pete Harlan
2008-10-22 22:42 ` Jakub Narebski [this message]
2008-10-23 7:43 ` Andreas Ericsson
2008-10-23 13:04 ` Nguyen Thai Ngoc Duy
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=m3d4hsi708.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@nedharvey.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.