You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/source/UserGuide/Tutorials/JobManagementAdvanced/index.rst
+18-5Lines changed: 18 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -335,16 +335,15 @@ Jobs that can (or should) run using more than 1 processor should be described as
335
335
using the "setNumberOfProcessors" method of the API::
336
336
337
337
j = Job()
338
-
j.setCPUTime(500)
339
-
j.setExecutable('echo',arguments='hello')
340
-
j.setExecutable('ls',arguments='-l')
341
-
j.setExecutable('echo', arguments='hello again')
342
-
j.setName('MP test')
338
+
...
343
339
j.setNumberOfProcessors(16)
344
340
345
341
Calling ``Job().setNumberOfProcessors()``, with a value bigger than 1,
346
342
will translate into adding also the "MultiProcessor" tag to the job description.
347
343
344
+
``Job().setNumberOfProcessors()`` takes at most 3 arguments, in this order:
345
+
``numberOfProcessors`` is the exact number of requested processors, ``minNumberOfProcessors`` is the minimum allowed, ``maxNumberOfProcessors`` the maximum.
346
+
348
347
Users can specify in the job descriptions NumberOfProcessors and WholeNode parameters, e.g.::
349
348
350
349
NumberOfProcessors = 16;
@@ -356,6 +355,20 @@ This will be translated internally into 16Processors and WholeNode tags.
356
355
This would allow resources (WN's) to put flexibly requirements on jobs to be taken, for example, avoiding single-core jobs on a multi-core nodes.
357
356
358
357
358
+
Setting memory limits
359
+
@@@@@@@@@@@@@@@@@@@@@
360
+
361
+
Jobs can (and probably should) set RAM limits.
362
+
using the "setRAMRequirements" method of the API::
363
+
364
+
j = Job()
365
+
...
366
+
j.setRAMRequirements(2, 4)
367
+
368
+
Calling ``Job().setRAMRequirements()`` takes 2 values, where the first is the minimum required amount of RAM (in GB) that the job requests.
369
+
The second value instead specifies the limit that should not be surpassed.
370
+
371
+
359
372
Submitting jobs with specifc requirements (e.g. GPU)
0 commit comments