Reference SCM Queue / Provisioner structure here: https://help.autodesk.com/view/SCM/ENU/?guid=SCM-UNDERSTAND-LAN-CONCEPT The performance of Provisioners (Insight solvers) can be a strong function of how new the hardware is and how many simultaneous jobs they are solving. The more simultaneous jobs, the more performance degrades. This is particularly strong with desktop solvers that have only 2 channels of RAM where the average solve time (in my testing) increases by about 48% when solving 2 jobs at the same time vs 1. The current (2.0) design of the SCM (i.e. job manager) does not allow for any kind of weighting or preference order for Provisioners. So if I have 6 Provisioners (solvers) all reporting the same Queue, they will take jobs to solve on a random basis. If a Provisioner is configured to be able to solve 2 or more jobs simultaneously, it could take on 2 or more jobs while another Provisioner is sitting idle. This is a poor use of resources. At a minimum, I'd like to see that all idle Provisioners get 1 job before any Provisioner gets a 2nd job. It would be even better is Provisioners could be ordered or weighted, so the fastest provisioners would be given (or allowed to take) work first. If this included a way to have a Provisioner in a priority list multiple times, with each entry having a different number of "current jobs" that would enable an optimum distribution of work, saving both time and energy (newer machines are more energy efficient).
Show More