Hv issue719 job manager threaded job start

[HansVRP]

No description provided.

[HansVRP]

@soxofaan maybe good to rediscuss from this point (local unit tests are passing)

[soxofaan]

some quick notes

[soxofaan]

by the way, I don't think you had to create a new PR, you just could have continued on #730 by pushing to its feature branch (we now have three open PRs for this feature I think, which gets a bit messy)

[HansVRP]

worked on your initial comments @soxofaan

currently checking why some unit tests are not passing

[soxofaan]

@soxofaan I do not think the failing unit test in 3.11 are due to my changes?

indeed, that problem has been fixed on master by now

[HansVRP]

One issue I still see now and want to resolve is that currently launching jobs (to queue them for start) is still tied in to the backend load.

This means than when running at full capacity you will not already 'precreate jobs' which can instantly start running

[soxofaan]

when running at full capacity you will not already 'precreate jobs' which can instantly start running

I'm not sure that pre-creating jobs instead of on the fly like we currently do will make that big of a difference as the time to create a job is usually negligible compared to the required time to start a job. Or do you experience different timings?

[HansVRP]

@soxofaan adjusted the unit tests and resolved the small bugs.

I also proposed to split off the _JobManagerWorkerThread

to allow it in the future to also contain alternative threads for downloading, jobworkerthreadpools, .....