On the deployement screen, we have Concurrency Lim...
# generals
Simon
11/18/2021, 6:00 PMOn the deployement screen, we have Concurrency Limit.
Let say I have 5 map reduced scripts and I set the Concurrency Limit to 10 for each of them, will it take the ressources from one another ? Will is slow down ? Or Currency Limit are independant by deployments ?
e
eblackey
11/18/2021, 7:22 PMYou have a concurrency limit at the account level based on things like Tier, SuiteCloud+ licenses. The scripts share that concurrency limit. You’re just specifying a limit that the particular script cannot go over.
k
KevinJ of Kansas
11/18/2021, 9:11 PMThink of processors as lanes on a highway - concurrency divides the jobs up on the map/reduce in order to use more highways.
SuiteCloud + licences control how many processors (lanes) you have available to drive down
KevinJ of Kansas
11/18/2021, 9:12 PMSo if you have 15 processors in your example - and you have 3 scripts with 10 concurrency limits and they all get queued at similar times - odds are one of the jobs is going to take 10 lanes - the other will take 5 until one of the first two jobs are done - then they will do the same split again until the jobs are finished
KevinJ of Kansas
11/18/2021, 9:12 PMDepending on the volume of traffic you need to move through the processes - those delays could be very minimal. Or they could be extensive.
KevinJ of Kansas
11/18/2021, 9:13 PMThe advantage to dropping a concurrency limit below your provisioned number of processors is it keeps long running processes from hogging all of the processors so that other jobs can run.
KevinJ of Kansas
11/18/2021, 9:13 PMAnother reason you might lower concurrency on a job is to preserve order of operations (I cringe at this for what it's worth - at that point just use a scheduled script)
r
Rebecca
11/23/2021, 4:06 PM@KevinJ of Kansas very nice explanation! I’m stealing this one.
s
Simon
11/23/2021, 4:08 PMI agree, it helped me understand better
5 Views