Sorry, I got your names flipped around. 

On Monday, February 27, 2017 at 11:53:08 AM UTC-8, [email protected] 
wrote:
>
> You are right Mahesh.  Will disabling the "Clean Working Directory" cause 
> old files to be left behind if it no longer exist in the source repository? 
>   I will give it a try but my wish it to have a configurable property where 
> I can set the number of concurrent threads to serve this fetching. 
> I am also curious where this code resides.  
>
> Thank you Mahesh and Ashwanth for replying. 
>
> Thanks,
> Keith
>
> On Sunday, February 26, 2017 at 11:51:21 PM UTC-8, Ashwanth Kumar wrote:
>>
>> I don't think he means the MDU Thread(s) but fetch process that happens 
>> as part of the preparing phase of a stage in a pipeline. Keith correct me 
>> If I'm wrong. 
>>
>> The SCM materials that get's checked out as part of the stage prep phase 
>> gets cloned (or) updated in a sequential manner isn't? Given the logs are 
>> also displayed in a sequence on the console.log. I'm curious though, is 
>> there a way we can make it parallel? 
>>
>> Keith, To reduce the material update process may be you can try disabling 
>> the "Clean Working Directory" on the given stage so Go need not fetch all 
>> materials over and over again when it gets scheduled on the same agent. It 
>> might reduce the time a little (based on a number of factors like how many 
>> materials get's updated for a single trigger of the pipeline, the lifetime 
>> of the agent etc.)
>>
>>
>> On Mon, Feb 27, 2017 at 9:47 AM, Mahesh Panchakasahriah <
>> [email protected]> wrote:
>>
>>> Hello,
>>>
>>> Material updates are not sequential, rather there are 10 threads to 
>>> handle updates at a given point of time. The number of threads can be 
>>> configured through the System Property *material.check.threads *which 
>>> defaults to 10.
>>>
>>> Why do you think the updates are sequential, are you facing any issues 
>>> with the material update?
>>>   
>>> Thanks,
>>> Mahesh
>>>
>>> On Saturday, February 25, 2017 at 12:18:17 AM UTC+5:30,
>>>
>>>> My pipeline has a list of greater than 20 materials, I am seeing that 
>>>> Go I fetching these materials one after another.  Is there a way that I 
>>>> can 
>>>> make these fetches concurrent? 
>>>> What other solutions you might have to shorten the fetch process. 
>>>> Thanks,
>>>> Keith
>>>>
>>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "go-cd" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to [email protected].
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> -- 
>>
>> Ashwanth Kumar / ashwanthkumar.in
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to