Git development
 help / color / mirror / Atom feed
From: Matthew Hughes <matthewhughes934@gmail.com>
To: "D. Ben Knoble" <ben.knoble@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Bash completion very slow in large repo
Date: Sat, 15 Aug 2026 20:52:46 +0100	[thread overview]
Message-ID: <aoDB9roVjgoTeG5l@desktop> (raw)
In-Reply-To: <CALnO6CAWA4szRqq_=1kAjB_y6WqA5zSyyMZzPmgnV7KGb+AS7Q@mail.gmail.com>

On Sat, Aug 15, 2026 at 10:17:19AM -0400, D. Ben Knoble wrote:
> Hi Matt, have you tried turning on "feature.manyFiles"? That enables a
> few things (like the fsmonitor) that might help in large repositories.

Ah, thanks for calling that out: I should've mentioned this is in a repo that's
already configured via `git-scalar(1)`, so it sets that specific option off,
but justifies:

> feature.manyFiles=false
> This disables the "many files" optimizations grouped under this feature config.
> The expectation is that all valuable optimizations are also set explicitly by
> Scalar config, and any differences are intentional.

Though also testing in a fresh repo with no scalar but that option on I didn't
see any significant performance change.

I'm also not sure e.g. `git ls-files --exclude-standard --others --directory`
knows about things like `fsmonitor`/the untracked cache, like e.g. `git status`
does (disclaimer: I'm not at all familiar enough with the code to justify that
claim, it's based purely on my qualitative experience, I'm also not sure if it
_could_ benefit from such things)

Cheers,
Matt

  reply	other threads:[~2026-08-15 19:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-14 18:55 Bash completion very slow in large repo Matthew Hughes
2026-08-15 14:17 ` D. Ben Knoble
2026-08-15 19:52   ` Matthew Hughes [this message]
2026-08-19 20:25 ` Matthew Hughes

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aoDB9roVjgoTeG5l@desktop \
    --to=matthewhughes934@gmail.com \
    --cc=ben.knoble@gmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox