From: "Han-Wen Nienhuys" <hanwenn@gmail.com>
To: git@vger.kernel.org
Subject: git branch performance problem?
Date: Wed, 10 Oct 2007 17:22:29 -0300 [thread overview]
Message-ID: <f329bf540710101322xdea6210x5576779f2efd89b7@mail.gmail.com> (raw)
Hello,
I'm seeing very slow performance with 'git-branch'. Is this the
canonical way to find out the current branch? ( I know I can look into
.git/HEAD, but how likely is that to break in the future?)
hanwen@lilypond:/tmp/z$ time git branch
* foo
master
real 0m0.307s
user 0m0.232s
sys 0m0.038s
hanwen@lilypond:/tmp/z$ git --version
git version 1.5.1.rc1.949.g322bc
On NFS this takes 5 seconds. Note that I have a humongous amount of
remotes, but those should not be examined without -r, right?
hanwen@lilypond:/tmp/z$ find .git/refs/remotes | wc -l
1856
--
Han-Wen Nienhuys - hanwen@xs4all.nl - http://www.xs4all.nl/~hanwen
next reply other threads:[~2007-10-10 20:22 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-10 20:22 Han-Wen Nienhuys [this message]
2007-10-10 20:44 ` git branch performance problem? Lars Hjemli
2007-10-10 21:17 ` Han-Wen Nienhuys
2007-10-10 21:24 ` Han-Wen Nienhuys
2007-10-10 21:30 ` Han-Wen Nienhuys
2007-10-10 21:39 ` J. Bruce Fields
2007-10-10 21:45 ` Lars Hjemli
2007-10-10 21:49 ` Han-Wen Nienhuys
2007-10-10 21:53 ` J. Bruce Fields
2007-10-10 22:01 ` Han-Wen Nienhuys
2007-10-10 21:53 ` Johannes Schindelin
2007-10-10 22:55 ` Spam: " Brandon Casey
2007-10-11 9:41 ` Mike Ralphson
2007-10-11 10:58 ` Johannes Schindelin
2007-10-10 23:39 ` Linus Torvalds
2007-10-11 2:26 ` Han-Wen Nienhuys
2007-10-11 6:41 ` Alex Riesen
2007-10-11 10:46 ` Johannes Schindelin
2007-10-11 13:11 ` Han-Wen Nienhuys
2007-10-11 15:16 ` Linus Torvalds
2007-10-12 17:19 ` Salikh Zakirov
2007-10-10 21:34 ` Lars Hjemli
2007-10-10 21:54 ` [PATCH] git-branch: only traverse the requested refs Lars Hjemli
2007-10-10 23:00 ` Johannes Schindelin
2007-10-10 23:30 ` Lars Hjemli
-- strict thread matches above, loose matches on Subject: below --
2007-10-12 17:32 git branch performance problem? Salikh Zakirov
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=f329bf540710101322xdea6210x5576779f2efd89b7@mail.gmail.com \
--to=hanwenn@gmail.com \
--cc=git@vger.kernel.org \
--cc=hanwen@xs4all.nl \
/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).