Re: js/partial-clone-connectivity-check (was: What's cooking in git.git (Apr 2019, #05; Thu, 25))

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Apr 25, 2019 at 03:16:57PM -0700, Josh Steadmon wrote:

> On 2019.04.25 19:15, Junio C Hamano wrote:
> > * js/partial-clone-connectivity-check (2019-04-21) 1 commit
> >   (merged to 'next' on 2019-04-25 at ebd8b4bffd)
> >  + clone: do faster object check for partial clones
> > 
> >  During an initial "git clone --depth=..." partial clone, it is
> >  pointless to spend cycles for a large portion of the connectivity
> >  check that enumerates and skips promisor objects (which by
> >  definition is all objects fetched from the other side).  This has
> >  been optimized out.
> > 
> >  Will merge to 'master'.
> 
> Peff asked for a perf test for this [1], but I haven't had time to write one
> yet. I can do that in a separate patch if you still want to merge this
> as-is.

I won't die without one, but it would be nice. It may also be that an
existing perf test, but I don't think we cover partial clones in t/perf
at all. Might be worth just a straight-up "git clone --filter=blob:none"
test.

Also, in the proposed merge message above, it should be --filter, not
--depth, right?

-Peff



[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux