[gridengine users] coordinating multiple queues...

[George Georgalis]

inline...

On Fri, Jun 1, 2012 at 3:46 PM, Rayson Ho <rayson at scalablelogic.com> wrote:

> On Fri, Jun 1, 2012 at 6:12 PM, George Georgalis <george at galis.org> wrote:
> > our understanding is that priority _only_ impacts which queue gets drawn
> > from when resources become available. That's correct, right?
>
> That's different than the definition in the manpage. I sent you the
> URL in my previous email - can you click on it and read it? It says:
>
> priority
>     The priority parameter specifies the nice(2) value at  which
>     jobs in this queue will be run...



Indeed, queue_conf(5) priority applies to nice values (-20<x<20). The
ambiguity is I was referring to qsub definition (-1023<x<1024), which
"Defines or redefines the priority of the job relative to other jobs."

I can make use of both, but I do not see how to set a default qsub per
queue priority? Is it possible?


> Thanks! never looked at that. Can you clarify what "suspension" means? is
> it
> > SIGSTOP; followed by SIGCONT when resources are free? As mentioned we
> don't
> > want jobs to swap out
>
> If you can't afford preempted jobs to be swapped out, one way to do it
> is to use the cgroup memory controller to change the kernel virtual
> memory manager's behavior.
>
> http://www.kernel.org/doc/Documentation/cgroups/memory.txt
>
>
> http://www.oracle.com/technetwork/articles/servers-storage-admin/resource-controllers-linux-1506602.html
>
>
> http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Resource_Management_Guide/ch01.html
>
> Grid Engine's cgroup integration is coming in Grid Engine 2011.11 update 1:
>
> http://blogs.scalablelogic.com/2012/05/grid-engine-cgroups-integration.html
>
> (Note that you can use cgroups with older versions of Grid Engine, but
> you won't get the full benefit of the Grid Engine cgroups
> integration.)
>

csgroups looks interesting, I even have kernel experience from 10 years
back.... unfortunately, due to many factors it's not something I can touch
in the foreseeable future. Getting away from ge-6.1 will be a challenge too.

since our nodes are actually VM containers on physical hosts. Probably the
easiest way to prevent swapping will be to limit the sum of available ram
to all containers to less than physical ram. Not a panacea, but should work
most of the time.

-George


>, but hadn't considered subordinate_list, since it is
> > not something we are familiar with. If my new understanding is correct,
> we
> > can forget about using injecting nice into qsub; and get the desired
> effect
> > with subordinate_list and queue priority alone? Is there any way (best
> way)
> > to prevent stopped jobs from swapping out?
> >
> > Regards,
> > -George
> >
> >
> >
> > --
> > George Georgalis, (415) 894-2710, http://www.galis.org/
>



-- 
George Georgalis, (415) 894-2710, http://www.galis.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gridengine.org/pipermail/users/attachments/20120601/9f622be0/attachment.html>