Jette, Moe wrote on Tue, Feb 22, 2011 at 01:02:56PM -0800: > If you want to put nodes into two partitions and favor some nodes for one > partition > and other nodes for the other partition then you'll need to hack the code. > You may > want to leverage the existing "Weight" field though. Perhaps have one > partition use > the weight and the other use the negative of the weight or something of that > sort.
how do i use the negative of the weight in a partition? or was that in reference to hack the code? > ________________________________________ > From: [email protected] [[email protected]] On > Behalf Of Chris Scheller [[email protected]] > Sent: Tuesday, February 22, 2011 12:40 PM > To: [email protected] > Subject: Re: [slurm-dev] node ordering? > > Jette, Moe wrote on Tue, Feb 22, 2011 at 10:38:18AM -0800: > > > > See the Node's Weight parameter in man slurm.conf. > > That can probably be used for what you want. > > i have read that several times today and i don't see how i can apply > that to what i want to do. since the weight is assigned to the node > and that node could be in multiple partitions i would need a different > weight per partition? > > > > > Weight The priority of the node for scheduling purposes. All > > things being equal, jobs will be > > allocated the nodes with the lowest weight which satisfies > > their requirements. For > > example, a heterogeneous collection of nodes might be placed > > into a single partition for > > greater system utilization, responsiveness and capability. It > > would be preferable to > > allocate smaller memory nodes rather than larger memory > > nodes if either will satisfy a > > job's requirements. The units of weight are arbitrary, but > > larger weights should be > > assigned to nodes with more processors, memory, disk space, > > higher processor speed, etc. > > Note that if a job allocation request can not be satisfied > > using the nodes with the low?$B!> > > est weight, the set of nodes with the next lowest weight > > is added to the set of nodes > > under consideration for use (repeat as needed for higher > > weight values). If you abso?$B!> > > lutely want to minimize the number of higher weight nodes > > allocated to a job (at a cost > > of higher scheduling overhead), give each node a distinct > > Weight value and they will be > > added to the pool of nodes being considered for scheduling > > individually. The default > > value is 1. > > > > > > ________________________________________ > > From: [email protected] [[email protected]] On > > Behalf Of Chris Scheller [[email protected]] > > Sent: Tuesday, February 22, 2011 10:18 AM > > To: slurm-dev > > Subject: [slurm-dev] node ordering? > > > > is it possible to specify an order to job distribution to nodes that > > are in more than one partition? for instance, i have 10 nodes and the > > default partition is 1 through 10 but i want to add a new partition > > that is 5 through 10 but i want the have jobs sent to the nodes in > > reverse order, 10 through 5. i can get close with the ordering of > > NodeName entries but not quite what i want. > > > > > > -- > > Chris Scheller > > Unix System Administrator > > Department of Biostatistics > > School of Public Health > > University of Michigan > > Phone: (734) 615-7439 > > Office: M4218 > > > > > > > > -- > Chris Scheller > Unix System Administrator > Department of Biostatistics > School of Public Health > University of Michigan > Phone: (734) 615-7439 > Office: M4218 > > > -- Chris Scheller Unix System Administrator Department of Biostatistics School of Public Health University of Michigan Phone: (734) 615-7439 Office: M4218
