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

Re: git status became very slow after upgrading git

From
Sean Allred <allred.sean@gmail.com>
Date
Feb 10, 2024, 17:06 UTC
Message-ID
<m05xyw9r92.fsf@epic96565.epic.com>
In-Reply-To
<CAK7MZG1MeeS5QNPog9oS+MbdKpkDXu61eVOszsC20Q=ik+Ng=g@mail.gmail.com>
Vijay Raghavan Aravamudhan <avijayr@gmail.com> writes:
Show 9 quoted lines
> What did you do before the bug happened? (Steps to reproduce your issue)
> 1. brew update which pulled in latest version of git
> 2. git status in a repository (without submodules)
>
> What did you expect to happen? (Expected behavior)
> git status should have been fast
>
> What happened instead? (Actual behavior)
> git status takes almost 5s to complete.

Thanks for the report. This isn't a whole lot of information to go on. At least, I'm not able to reproduce locally with a trivial repository:

    git init
    echo foo > file
    git add file
    git commit -mtest
    git status

If you're able to reproduce, can you re-run `git status` with tracing enabled and provide your output?

    GIT_TRACE=1 GIT_TRACE_SETUP=1 GIT_TRACE_PERFORMANCE=1 git status

If you can provide reproduction instructions that start with `git init`, that would also help. It may take some time for you, but it'll take less time than folks on this list taking shots in the dark :-)

-- Sean Allred

Previous: Vijay Raghavan AravamudhanNext: Vijay Raghavan Aravamudhan
Message 2 of 5 in “git status became very slow after upgrading git”
  1. Vijay Raghavan AravamudhanFeb 10, 2024
  2. Sean AllredFeb 10, 2024
  3. Vijay Raghavan AravamudhanFeb 10, 2024
  4. Sean AllredFeb 10, 2024
  5. Vijay Raghavan AravamudhanFeb 10, 2024

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.