It is normal for Synda to be running a few jobs (each defined by "synda install -s ...") at once. When running two jobs, I have seen (with "synda watch") that sometimes only one job is active, i.e. all files being downloaded, belong to that one job.
Sometimes one server is much slower than another one. So good performance requires that each job has a few, e.g. 4, files being actively downloaded at any time.
I suggest that the parameter max_parallel_download apply separately to each job.
In the future 3.4 release, a new feature for asynchronous downloads will be implemented. It is built on the asyncio library. We measured higher performances that we hope near to be the best that can be reached.
It is normal for Synda to be running a few jobs (each defined by "synda install -s ...") at once. When running two jobs, I have seen (with "synda watch") that sometimes only one job is active, i.e. all files being downloaded, belong to that one job.
Sometimes one server is much slower than another one. So good performance requires that each job has a few, e.g. 4, files being actively downloaded at any time.
I suggest that the parameter max_parallel_download apply separately to each job.