[torquedev] [Bug 67] Support for counted resources on nodes

bugzilla-daemon at supercluster.org bugzilla-daemon at supercluster.org
Wed Aug 4 10:47:08 MDT 2010


http://www.clusterresources.com/bugzilla/show_bug.cgi?id=67

--- Comment #24 from Simon Toth <SimonT at mail.muni.cz> 2010-08-04 10:47:08 MDT ---
(In reply to comment #23)
> (In reply to comment #17)
> > Created an attachment (id=40)
 --> (http://www.clusterresources.com/bugzilla/attachment.cgi?id=40) [details]
[details]
> > Resources checking logic
> > 
> > Additional logic to schedule resource requests passed through 
> >   qsub -l resource=value
> > 
> > This patch adds support for -l resource=value requests combined with nodespec.
> > 
> > Example:
> >   qsub -l nodes=10 -l ncpus=4 -l mem=4G
> > 
> > 
> > 
> > Two types of resources are supported. Per-proc and per-node.
> > 
> > Per-proc resources are counted for each process:
> >   -l nodes=1:ppn=2:ncpus=3
> >   if ncpus are per-proc then this is request for 2 processes, 3 cpus each = 6
> > cpus total
> > 
> > Per-node resources are counted for each node:
> >   -l nodes=1:ppn=2:mem=1G
> >   if mem is per-node then this is request for 2 processes, 1G memory on node =
> > 1G memory total
> > 
> > per-proc and per-node are set using flag in the resc_def_all.c file.
> 
> This is where some of the keyword ambiguity affects things. ppn is processors
> per node. That is how TORQUE looks at ppn internally. Virtually there is no
> difference between ppn and ncpus.

There are no ncpus in Torque server. The only thing that server understands is
ppn. As already discussed several times in the mailing list. PPN doesn't have
the semantics of either processor or processes.

-- 
Configure bugmail: http://www.clusterresources.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


More information about the torquedev mailing list