Jim, I think that NODEALLOCATIONPOLICY CPULOAD is the easiest one to implement.
David On Tue, May 17, 2011 at 1:19 PM, Jim Kusznir <[email protected]> wrote: > Hi all: > > I have a user who is requesting that the scheduler system be modified > such that jobs are not packed in by default. On our cluster, it is > rarely running at or near 100%. This user would prefer that only one > job is run per node unless all the nodes are full; at which point, it > can start packing things in more closely. > > I thought this is most aptly controlled by NODEALLOCATIONPOLICY, which > I have set to MINRESOURCE. I do have some nodes that have IB, and > some nodes that are 16-core nodes with twice the ram per core, but the > majority of my nodes are just 8-core/8GB ram nodes, and those are fine > for the majority of jobs/users. So I want to make sure by default, > those are used unless they don't meet the specified resources, or > they're already busy (and the other nodes aren't). > > So, Is NODEALLOCATIONPOLICY the setting I should be looking at? What > exactly is MINRESOURCE's policy for job packing? > > --Jim > _______________________________________________ > mauiusers mailing list > [email protected] > http://www.supercluster.org/mailman/listinfo/mauiusers > _______________________________________________ mauiusers mailing list [email protected] http://www.supercluster.org/mailman/listinfo/mauiusers
