git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: git-fetching from a big repository is slow
Date: Thu, 14 Dec 2006 12:41:38 -0800	[thread overview]
Message-ID: <7v8xha2osd.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: Pine.LNX.4.63.0612141732410.3635@wbgn013.biozentrum.uni-wuerzburg.de

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

> git-show-ref traverses every single _local_ tag when called. This is to 
> overcome the problem that tags can be packed now, so a simple file 
> existence check is not sufficient.

Is "traverses every single _local_ tag" a fact?  It might go
through every single _local_ (possibly stale) packed tag in
memory but it should not traverse $GIT_DIR/refs/tags.

If I recall correctly, show-ref (1) first checks the filesystem
"$GIT_DIR/$named_ref" and says Ok if found and valid; otherwise
(2) checks packed refs (reads $GIT_DIR/packed-refs if not
already).  So that would be at most one open (which may fail in
(1)) and one open+read (in (2)).  Unless we are talking about
fork+exec overhead, that "traverse" should be reasonably fast.

Where is the bottleneck?

  reply	other threads:[~2006-12-14 20:41 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-14 13:40 git-fetching from a big repository is slow Andy Parkins
2006-12-14 13:53 ` Andreas Ericsson
2006-12-14 14:14   ` Johannes Schindelin
2006-12-14 15:06     ` Andreas Ericsson
2006-12-14 19:05       ` Geert Bosch
2006-12-14 19:46         ` Shawn Pearce
2006-12-14 22:12           ` Horst H. von Brand
2006-12-14 22:38             ` Shawn Pearce
2006-12-15 21:49               ` Pazu
2006-12-16 13:32                 ` Robin Rosenberg
2006-12-14 23:01           ` Geert Bosch
2006-12-14 23:15           ` Johannes Schindelin
2006-12-14 23:29             ` Shawn Pearce
2006-12-15  0:07               ` Johannes Schindelin
2006-12-15  0:42                 ` Shawn Pearce
2006-12-15  2:26             ` Nicolas Pitre
2006-12-14 22:28         ` Andreas Ericsson
2006-12-14 15:18   ` Andy Parkins
2006-12-14 15:45     ` Han-Wen Nienhuys
2006-12-14 16:20       ` Andy Parkins
2006-12-14 16:34         ` Johannes Schindelin
2006-12-14 20:41           ` Junio C Hamano [this message]
2006-12-14 23:26             ` Johannes Schindelin
2006-12-15  0:38               ` Junio C Hamano
2006-12-14 18:14   ` Nicolas Pitre

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=7v8xha2osd.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=Johannes.Schindelin@gmx.de \
    --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).