Re: [PATCH] Add fetch.recurseSubmoduleParallelism config option

From: Stefan Beller <sbeller@google.com>
Date: Oct 16, 2015, 17:04 UTC
Message-ID: <CAGZ79kZDMawq6f3Jet0o-93-vSamy3skji63brdT3puzaLty5Q@mail.gmail.com>
In-Reply-To: <xmqqa8rnbq9k.fsf@gitster.mtv.corp.google.com>

On Mon, Oct 12, 2015 at 4:50 PM, Junio C Hamano <gitster@pobox.com> wrote:

Show 9 quoted lines

> Stefan Beller <sbeller@google.com> writes:
>
>> There is core.preloadIndex to enable parallel index preload, but
>> that is boolean and not giving fine control to the user. We want to give
>> fine control to the user here I'd assume.
>
> I'd approach this as "fetching multiple submodules at a time", if I
> were deciding its name.
>

so maybe
    fetch.recurseSubmoduleJobs
    fetch.submoduleJobs
    fetch.jobs
    fetch.connectionsToUse

Eventually we want to also be parallel in git fetch --all, when using the latter two we could reuse these then too, no need to support different options for fetch --all and fetch --recurseSubmodules.

Show 5 quoted lines

> So if you want
>
>     [submodule]
>         fetchParallel = 16
>         updateParallel = 4

So you would have different settings here for only slightly different things? So the series I sent out yesterday evening, would make use of updateParallel for parallel cloning then instead?