Re: using tree as attribute source is slow, was Re: Help troubleshoot performance regression cloning with depth: git 2.44 vs git 2.42

From: Dhruva Krishnamurthy <dhruvakm@gmail.com>
Date: May 3, 2024, 05:37 UTC
Message-ID: <CAKOHPA==xgRBLXmyURkdZ9X4LqQoBHYy=XD0Q_KTQHbK54DOFg@mail.gmail.com>
In-Reply-To: <xmqqbk5ndiqk.fsf@gitster.g>

On Thu, May 2, 2024 at 2:08 PM Junio C Hamano <gitster@pobox.com> wrote:

Show 10 quoted lines

> We could drop [1/2] from the series in the meantime to make it a
> GitLab installation specific issue where they explicitly use
> attr.tree to point at HEAD ;-) That is not solving anything for
> those who set attr.tree (in a sense, they are buying the feature
> with overhead of reading attributes from the named tree), but at
> least for most people who are used to seeing the bare repository
> ignoring the attributes, it would be an improvement to drop the
> "bare repositories the tree of the HEAD commit is used to look up
> attributes files by default" half from the series.
>

A hack (without knowing side effects if any) is to use an empty tree for attr source: $ git config --add attr.tree $(git hash-object -t tree /dev/null)

This gives me performance comparable to git 2.42