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

Re: Git status performance on PS (command prompt)

From
Christian Couder <christian.couder@gmail.com>
Date
Feb 13, 2017, 06:12 UTC
Message-ID
<CAP8UFD2Ve4WvyBg-DDye4Bpwb=MjB8P6V6mQdWDPbiwnVKovzg@mail.gmail.com>
In-Reply-To
<20170212164650.u7frv234kmu5hm7r@genre.crustytoothpaste.net>

On Sun, Feb 12, 2017 at 5:46 PM, brian m. carlson <sandals@crustytoothpaste.net> wrote:

> On Sun, Feb 12, 2017 at 04:53:47PM +0100, Mark Gaiser wrote:
[...]
>> I did a bit of profiling in git to figure out where this slowdown comes from.
>> Callgrind tells me that "read_directory_recursive" takes up ~62% of the time.
>> Within that call the function "last_exclude_matching_from_list" takes
>> up 49% of the time it takes to run "git status --porcelain -b".
The core.untrackedCache config option may help.
Previous: brian m. carlson
Message 3 of 3 in “Git status performance on PS (command prompt)”
  1. Mark GaiserFeb 12, 2017
  2. brian m. carlsonFeb 12, 2017
  3. Christian CouderFeb 13, 2017

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.