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

Re: git-gui: How to configure for use in gigantic projects?

From
KTKonstantin Tokarev <annulen@yandex.ru>
Date
Oct 30, 2020, 10:30 UTC
Message-ID
<445251604053314@mail.yandex.ru>
In-Reply-To
<CAGr--=KpNaPFjMOzXzF382cv1p58nMoOPXAm0MCdA8WZMBznVA@mail.gmail.com>
30.10.2020, 13:16, "Birger Skogeng Pedersen" <birger.sp@gmail.com>:
Show 19 quoted lines
> Hi,
>
> I would like to use git gui for a project. The problem is that the
> repository directory is really gigantic. Doing a scan (F5) takes a
> couple of minutes to finish.
>
> I would like the scan to only focus on files that are specifically
> added to the index. In git I do this:
>
> git config status.showUntrackedFiles no
>
> git status will then only show status of files that I have
> specifically added. So git status completion is instant.
>
> But this configuration appears to have no effect on git-gui. The scan
> is just as slow as before.
>
> Anything I can do to make git-gui only scan files that are
> specifically added, and not look through the whole directory?

FWIW, there are better ways to improve performance of git status without hiding untracked files (which are useful to see when new files are added):

* Add all uninteresting files and directories to .gitignore
* Use fast storage for git repository, e.g. NVME-based
* If your OS can handle filesystem cache efficiently (e.g., Linux) make sure 
there is enough of free RAM for caches and all repeated operations on
same files and directories will speed up dramatically
* If your OS cannot handle filesystem cache efficiently (e.g. Windows) consider
using different OS for development
* If overall performance is still not sufficient, consider using fsmonitor hook [1]
[1] https://github.blog/2018-04-05-git-217-released/#speeding-up-status-with-watchman

--  Regards, Konstantin

Previous: Birger Skogeng PedersenNext: Pratyush Yadav
Message 2 of 5 in “git-gui: How to configure for use in gigantic projects?”
  1. Birger Skogeng PedersenOct 30, 2020
  2. Konstantin TokarevOct 30, 2020
  3. Pratyush YadavOct 30, 2020
  4. Birger Skogeng PedersenOct 30, 2020
  5. Marc BranchaudOct 30, 2020

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.