As of now the --concurrency-limit option is splitting the commands by chunks. However, it waits for all the processes in the chunk to complete before starting the next chunk. In case one site is slow to execute the command, it will delay then next processes for no reason.
We should uses the processes in a better way to be sure we always use the maximum number of processes specified by --concurrency-limit option.
vbouchet31
commented
2 years ago
As of now the --concurrency-limit option is splitting the commands by chunks. However, it waits for all the processes in the chunk to complete before starting the next chunk. In case one site is slow to execute the command, it will delay then next processes for no reason. We should uses the processes in a better way to be sure we always use the maximum number of processes specified by --concurrency-limit option.