Hello Keith, The property *material.check.threads* to control the number of threads for material updates is used only on GoCD server. You seem to be looking for concurrent updates on the agent side which is not possible as of now, updates on the agent is sequential. Thanks, Mahesh
On Tuesday, February 28, 2017 at 5:46:36 AM UTC+5:30, > > Hey Mahesh, > > Could you share with me where this property can be found I would like see > if changing it would solve my issue, I tried looking for any documentation > on it, but to no avail. > > Thanks, > Keith > > > On Sunday, February 26, 2017 at 8:17:11 PM UTC-8, Mahesh Panchakasahriah > 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.
