Changing the identity of "First Available"

[jwk]

How can one specify the compute priority in the WebMO queue? Currently (WebMO 23) the First available is an older, slower machine, with newer, faster machines lower on the queue list. I would rather define the queue in order of descending compute speed, if possible. Having users manually choose the faster machine is not a general solution because under some circumstances, for example a lab class submitting multiple 5-min/4-proc jobs, that machine may be fully occupied with multiple jobs.

[schmidt]

There is no good way to do this, unfortunately. I believe the "best" way is simply to DELETE the old server and then re-add it. This should move it later in the queue. (Tweaks to "remote servers" are few and far between these days, since almost all usage is now either "fat" single machines or HPC clusters.)

[jwk]

Thanks, J.R. Yes, a Delete-Re-add move is good for changing the queue order of the remote servers. But the problem here is the WebMO server itself is the "old" one, and that one cannot be deleted and re-added. In the context of on-premises webmo servers then, the best answer is to move webmo onto a big, fast server, letting the slower ones pick up overflow jobs from large classes.