I think of the concept of "slots" as being an attribute of a host....something like the max number of SGE jobs that should run on the host. Generally slots would be equal to CPUs. I don't understand the meaning of slots when applied to a queue.
Assume all hosts on the cluster have 4 CPUs. Can I set up a queue that will only allow 4 of my cpu-intensive simulations to run on any host and another queue that will allow essentailly an unlimited (typically maybe 4) of my servers (very low impact) to also run simultaneously with the simulations. Each queue should have access to all hosts on the cluster. On Tue, Apr 3, 2012 at 12:26 PM, Rayson Ho <[email protected]> wrote: > (CCing the list - you don't want to miss the answers from Reuti & > other experienced Grid Engine experts on the list!) > > 1) You can set "slots" to anything - as long as it is a natural > number. It can be greater than the number of processors in the server. > > 2) I don't fully understand this "environment server" setup - is it a > process running on the local machine, or a remote process providing > Monte Carlo simulation as a Service (MCSaaS :-D )?? > > And if it is a local process, then what is the issue of starting it by > Grid Engine, so that resource accounting would work as expected?? > > Rayson > > > > > On Tue, Apr 3, 2012 at 1:18 PM, Earl Lazarus <[email protected]> > wrote: > > But doesn't it come down to the slots available on a host. Doesn't the > host > > have a slot limit equal to the number of CPUs? If I fill them with > > "environment servers", there is no room for my simulations to execute. > > I'm clearly missing something important in how SGE can be make to work. > > > > > > On Tue, Apr 3, 2012 at 12:14 PM, Rayson Ho <[email protected]> > wrote: > >> > >> On Tue, Apr 3, 2012 at 12:56 PM, Earl Lazarus <[email protected]> > >> wrote: > >> > Bottom line...I need to pre-position some executables on each host > >> > without > >> > consuming slots. > >> > >> How about setting up queues for these kinds of jobs that don't really > >> consume much resources?? You can set an arbitrary large number of > >> slots for each queue, but with a low job resource limit. > >> > >> > Note that I tried to kick them off in a script of the form: > >> > > >> > sppe & > >> > exit > >> > > >> > but Grid Engine monitors jobs placed in the background and kills them! > >> > >> As soon as the job script finishes, Grid Engine kills the job. This is > >> the designed behavior. > >> > >> Rayson > >> > >> > > >> > The possibility of avoiding Grid Engine entirely and kicking them off > >> > with > >> > rsh/ssh is something we want to avoid. > >> > > >> > earl > >> > > >> > _______________________________________________ > >> > users mailing list > >> > [email protected] > >> > https://gridengine.org/mailman/listinfo/users > >> > > > > > >
_______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
