[torqueusers] resource "nodect"

Garrick Staples garrick at usc.edu
Mon Feb 14 15:24:38 MST 2005


On Sat, Feb 12, 2005 at 09:24:26AM +0530, Amitay Isaacs alleged:
> Hi,
> 
> Garrick Staples wrote:
> 
> >>>set queue workq resources_default.nodect = 1
> >>
> >>default node count when no explicit node count was asked for by the job.
> >
> >
> >I'm not sure that a default nodect has any meaning, since you don't 
> >explicitly
> >request a "nodect" attribute in your job.  Instead, you set a default 
> >"nodes"
> >attribute.  Note that "nodes" is a string and not a number; so you can do
> >things like "nodes=1:ppn=1"
> >
> 
> In case you have default nodect set to 1, users can submit single CPU
> jobs without specifying "-l nodes" qualifier. The problem with that
> is all the jobs submitted without the qualifier get scheduled on a
> single node, thus overloading the node.

Again, I don't think default.nodect=1 is what you want.  I think you want
default.nodes=1

But that behaviour sounds weird.  Which scheduler are you using?

-- 
Garrick Staples, Linux/HPCC Administrator
University of Southern California
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://www.supercluster.org/pipermail/torqueusers/attachments/20050214/ec3c280b/attachment.bin


More information about the torqueusers mailing list