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

Re: name-rev --stdin is slow

From
Daniel Barkalow <barkalow@iabervon.org>
Date
Jun 19, 2008, 22:03 UTC
Message-ID
<alpine.LNX.1.00.0806191755510.19665@iabervon.org>
In-Reply-To
<485ACB34.2020901@gmail.com>
On Thu, 19 Jun 2008, Lea Wiemann wrote:
Show 6 quoted lines
> name-rev --stdin has some really high start-up time.  The example below is on
> my git.git branch.  Is this unavoidable to make name-rev fast for naming high
> numbers of revisions -- i.e. is it about amortization? Still, 0.7 seconds
> seems pretty excessive, and on linux-2.6 it even takes 6 seconds.
> 
> Anyone care to look into it?

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, which means that each request is slower, at least until it's cached everything that you turn out to care about.

	-Daniel
*This .sig left intentionally blank*
Previous: Lea WiemannNext: Lea Wiemann
Message 2 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.