All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lea Wiemann <lewiemann@gmail.com>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: name-rev --stdin is slow
Date: Fri, 20 Jun 2008 00:09:18 +0200	[thread overview]
Message-ID: <485AD90E.6000309@gmail.com> (raw)
In-Reply-To: <alpine.LNX.1.00.0806191755510.19665@iabervon.org>

Daniel Barkalow wrote:
> Actually, I think it's the reverse: without --stdin, name-rev can do a 
> first pass that lets it eliminate a lot of data from consideration; with 
> --stdin, it doesn't know if an item it hasn't seen is going to need some 
> data, and so it's conservative and doesn't eliminate anything,

Are you sure that's the case?  time git-name-rev --stdin < /dev/null 
gives the same high startup time without looking up anything.

Anyways, it would be great if someone could try to fix that, since a 
6-second startup time on a repository like linux-2.6 makes the --stdin 
option unusable for applications like gitweb (for which it would 
actually be quite useful to reduce the number of forks).

-- Lea

  reply	other threads:[~2008-06-19 22:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-19 21:10 name-rev --stdin is slow Lea Wiemann
2008-06-19 22:03 ` Daniel Barkalow
2008-06-19 22:09   ` Lea Wiemann [this message]
2008-06-19 23:00     ` Daniel Barkalow

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=485AD90E.6000309@gmail.com \
    --to=lewiemann@gmail.com \
    --cc=barkalow@iabervon.org \
    --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.