[torquedev] [Bug 93] Resource management semantics of Torque need to be well defined

bugzilla-daemon at supercluster.org bugzilla-daemon at supercluster.org
Tue Dec 7 09:26:54 MST 2010


--- Comment #21 from Ken Nielson <knielson at adaptivecomputing.com> 2010-12-07 09:26:54 MST ---
(In reply to comment #19)
> I posted this in the torquedev thread generated by bugzilla for this bug:
> 2010/12/6 Michel Béland <michel.beland at rqchp.qc.ca>:
> > Later, they introduced -lselect and deprecated -lnodes altogether. Now
> > one can ask for -lselect=10:ncpus=8:mpiprocs=2:ompthread=4 to get the
> > same result, if I remember correctly, but I think that I liked ppn and
> > cpp better...
> I remember there was talk from some of the TORQUE developers at
> adaptive about adding a "select" statement to TORQUE.  Whatever
> happened to that?  I think it would be great if we could add in a
> select feature that is compatible (or at least mostly compatible) with
> the PBS Pro select.  Maybe Šimon Tóth's work could get us partially
> there.

I was reminded of this at SC'10. Over the summer when we started looking at
putting select in the TORQUE resource manager we realized this would actually
be best handled by the Scheduler. Even so there seems to be a need to have some
basic support for select at the RM level.

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