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

Re: Why is --pretty=format: so slow?

From
Junio C Hamano <gitster@pobox.com>
Date
Nov 4, 2007, 04:22 UTC
Message-ID
<7vmytuvdvq.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<18221.16318.785162.44769@cargo.ozlabs.ibm.com>
Paul Mackerras <paulus@samba.org> writes:
> Strace seems to indicate that git log is doing at least one sequence
> of open, fstat64, fcntl64, getdents64 and close for each line of
> output in the --pretty=format: cases, but not in the other cases.

I bet that is coming from doing find_unique_abbrev() to fill fields %h, %t and %p, even when the output format does not ask for any of them.

Dscho, can we stop calling find_unique_abbrev() unconditionally before being asked?

Previous: Paul MackerrasNext: René Scharfe
Message 2 of 5 in “Why is --pretty=format: so slow?”
  1. Paul MackerrasNov 4, 2007
  2. Junio C HamanoNov 4, 2007
  3. René ScharfeNov 4, 2007
  4. Junio C HamanoNov 4, 2007
  5. René ScharfeNov 4, 2007

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.