Re: [RFC/PATCH] read-cache: write all indexes with the same permissions
- From
Christian Couder <christian.couder@gmail.com>
- Date
- Nov 17, 2018, 06:52 UTC
- Message-ID
- <CAP8UFD3sX4YPmyXtxbcL3-TZEyd_fq7MuSZkYeNGvqswuF4Ncw@mail.gmail.com>
- In-Reply-To
- <CACsJy8DS1JyuRFyKhVRnVt+ax40+yyv-OVknfQ82OO9jtMeK8g@mail.gmail.com>
On Fri, Nov 16, 2018 at 8:20 PM Duy Nguyen <pclouds@gmail.com> wrote:
Show 7 quoted lines
> > On Fri, Nov 16, 2018 at 8:07 PM SZEDER Gábor <szeder.dev@gmail.com> wrote: > > > With the default 20% threshold a new shared index is written rather > > frequently with our usual small test-repos: > > Side note. Split index is definitely not meant for small repos.
I very much agree with that. It makes sense to use them only for big repos and big repos usually don't pass a 20% threshold very often.
> But > maybe we should have a lower limit (in terms of absolute number of > entries) that prevent splitting. This splitting seems excessive.
I would agree if split index was the default mode or if our goal was to eventually make it the default mode.
Or it could be a new "mixed" mode for core.splitIndex (which might eventually become the default mode) to have no split-index as long as the repo stays under a lower limit and to automatically use split-index when the repo gets over the limit.