[torquedev] [Bug 116] New: enable routing depending on number of requested processors
bugzilla-daemon at supercluster.org
bugzilla-daemon at supercluster.org
Wed Mar 9 17:26:14 MST 2011
http://www.clusterresources.com/bugzilla/show_bug.cgi?id=116
Summary: enable routing depending on number of requested
processors
Product: TORQUE
Version: 2.5.x
Platform: PC
OS/Version: Linux
Status: NEW
Severity: enhancement
Priority: P5
Component: pbs_server
AssignedTo: dbeer at adaptivecomputing.com
ReportedBy: siegert at sfu.ca
CC: torquedev at supercluster.org
Estimated Hours: 0.0
Created an attachment (id=74)
--> (http://www.clusterresources.com/bugzilla/attachment.cgi?id=74)
torque-2.5.5-procct.patch
The attached patch creates a new resource "procct" that counts the number of
requested processors in nodes and/or procs requests. This allows configuration
of routing queues depending on the number of requested processors, e.g.,
create queue default
set queue default queue_type = Route
set queue default route_destinations = q1
set queue default route_destinations += qsmall
set queue default route_destinations += qlarge
create queue q1
set queue q1 queue_type = Execution
set queue q1 resources_max.procct = 1
create queue qsmall
set queue qsmall queue_type = Execution
set queue qsmall resources_max.procct = 128
set queue qsmall resources_min.procct = 2
create queue qlarge
set queue qlarge queue_type = Execution
set queue qlarge resources_min.procct = 129
set server default_queue = default
For requests of the form -l nodes=x:ppn=y -l procs=z procct is set to x*y+z.
The value is unset after the job has been assigned to a queue, otherwise the
job is not run by moab (I have not tested maui) because moab does not know how
to handle the procct resource.
Furthermore, the environment variable PBS_NP is set to the number of requested
processors for use in submission scripts.
- Martin
--
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