Hi, > Am 02.05.2017 um 15:11 schrieb [email protected]: > > we run SGE 8.1.9 in a cluster with many multi-core machines and some GPU > machines. We were able to configure different queues with different complexes > and the scheduling works fine in general. What I'm not yet happy with is the > way the priority is calculated. > > A typical user will submit a few GPU jobs and many non-GPU jobs. The two > queues are strictly separated - no GPU jobs will run on a non-GPU machine and > no non-GPU jobs will run on a GPU machine. Unfortunately, the regular > CPU-jobs that run on non-GPU machines seem to reduce the priority of the > pending GPU jobs. This seems to penalize GPU-users even if their GPU > consumption has been very low for a long time.
Yes, that's understandable. > Since the GPU-per-user ratio is very low (~1.5), I would like the SGE to keep > scheduling the CPU jobs as before, but do something different for GPU jobs. > Ideally, I would like it to ignore all non-GPU usage when calculating > priority for GPU jobs. > > What is the best mechanism to achieve this separation? I could install two > instances of SGE (one for GPU, one for non-GPU queues) so that their > schedulers are 100% independent, but it is difficult to maintain and I would > prefer anything more "native". Are you using projects right now? Either voluntarily of forced by a JSV, the GPU jobs could be assigned to a (different) project in a share tree policy and get a different scheduling behavior this way. -- Reuti _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
