I think in my case I can just set up a queue with a number of instances equal to the number of licenses I have. I'm not so much worried about maximum efficiency as avoiding having jobs fail because of license oversubscription.
Dealing with host-based licensing is a feature Qube advertises - it comes up reasonably often with vfx software. Another feature which I couldn't figure out how to achieve is per-host dependencies (particularly in array dependencies) - if one task is going to generate a load of data for another task to consume then I could write it all to the local tmp drive if I know the dependent task will run on the same host rather than pushing it across the network. Instead I just wrap those tasks up into a single task submission which is fine for single dependencies but it would be nice to have something more flexible. The content of this e-mail (including any attachments) is strictly confidential and may be commercially sensitive. If you are not, or believe you may not be, the intended recipient, please advise the sender immediately by return e-mail, delete this e-mail and destroy any copies. _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
