On Fri, Jun 1, 2012 at 6:12 PM, George Georgalis <[email protected]> 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...
> 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.)
Rayson
>, 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/
_______________________________________________
users mailing list
[email protected]
https://gridengine.org/mailman/listinfo/users
