From: Petr Baudis <pasky@suse.cz>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Junio C Hamano <junkio@cox.net>,
Peter Eriksen <s022018@student.dtu.dk>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Bottlenecks in git merge
Date: Wed, 1 Feb 2006 01:50:35 +0100 [thread overview]
Message-ID: <20060201005035.GD31278@pasky.or.cz> (raw)
In-Reply-To: <Pine.LNX.4.64.0601311533040.7301@g5.osdl.org>
Dear diary, on Wed, Feb 01, 2006 at 12:45:27AM CET, I got a letter
where Linus Torvalds <torvalds@osdl.org> said that...
> It would be interesting to see how big the "resolve 850 files" part is vs
> the "check out 10k+ files" is.
See my other mail.
> In particular, if the "resolve 850 files" is a noticeable portion of it,
> then the right thing to do may be to just re-write git-merge-one-file.sh
> in C. Right now, almost _all_ of the expense of that thing is just the
> shell interpreter startup. The actual actions it does are usually fairly
> cheap.
Nope.
xpasky@machine[0:0]~/linux-2.6.git$ echo -e '#!/bin/sh\n/bin/true' >r && chmod a+x r
xpasky@machine[0:0]~/linux-2.6.git$ time git-merge-index -o ./r -a
real 0m3.827s
user 0m1.788s
sys 0m2.004s
xpasky@machine[0:0]~/linux-2.6.git$ time git-merge-index -o ~/git-pb/git-merge-one-file -a
[lots of "Removing"]
real 1m21.773s
user 0m30.806s
sys 0m13.248s
The costs are apparently in git-update-index, not in the shell.
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
Of the 3 great composers Mozart tells us what it's like to be human,
Beethoven tells us what it's like to be Beethoven and Bach tells us
what it's like to be the universe. -- Douglas Adams
next prev parent reply other threads:[~2006-02-01 0:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-31 21:33 Bottlenecks in git merge Peter Eriksen
2006-01-31 23:06 ` Junio C Hamano
2006-01-31 23:35 ` Petr Baudis
2006-02-01 0:43 ` Junio C Hamano
2006-01-31 23:45 ` Linus Torvalds
2006-02-01 0:50 ` Petr Baudis [this message]
2006-02-01 1:04 ` Linus Torvalds
2006-01-31 23:27 ` Petr Baudis
2006-02-04 7:31 ` [PATCH] read-tree --aggressive Junio C Hamano
2006-02-04 11:52 ` Peter Eriksen
2006-02-04 12:56 ` Junio C Hamano
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=20060201005035.GD31278@pasky.or.cz \
--to=pasky@suse.cz \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=s022018@student.dtu.dk \
--cc=torvalds@osdl.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).