git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: name-rev --stdin is slow

From
LWLea Wiemann <lewiemann@gmail.com>
Date
Jun 19, 2008, 22:09 UTC
Message-ID
<485AD90E.6000309@gmail.com>
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
Previous: Daniel BarkalowNext: Daniel Barkalow
Message 3 of 4 in “name-rev --stdin is slow”
  1. Lea WiemannJun 19, 2008
  2. Daniel BarkalowJun 19, 2008
  3. Lea WiemannJun 19, 2008
  4. Daniel BarkalowJun 19, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.