Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
S
Slurm
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
tud-zih-energy
Slurm
Commits
dbf8be11
Commit
dbf8be11
authored
16 years ago
by
Moe Jette
Browse files
Options
Downloads
Patches
Plain Diff
clarify use of partition shared option
parent
e0189e8c
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/man/man5/slurm.conf.5
+40
-24
40 additions, 24 deletions
doc/man/man5/slurm.conf.5
with
40 additions
and
24 deletions
doc/man/man5/slurm.conf.5
+
40
−
24
View file @
dbf8be11
...
@@ -1535,32 +1535,48 @@ The default value is "NO".
...
@@ -1535,32 +1535,48 @@ The default value is "NO".
Controls the ability of the partition to execute more than one job at a
Controls the ability of the partition to execute more than one job at a
time on each resource (node, socket or core depending upon the value
time on each resource (node, socket or core depending upon the value
of \fBSelectTypeParameters\fR).
of \fBSelectTypeParameters\fR).
Possible values are "EXCLUSIVE", "FORCE", "YES", and "NO".
If resources are to be shared, avoiding memory over\-subscription
"EXCLUSIVE" allocates entire nodes to jobs even with
is very important.
select/cons_res configured.
\fBSelectTypeParameters\fR should be configured to treat
memory as a consumable resource and the \fB\-\-mem\fR option
should be used for job allocations.
For more information see the following web page:
\fIhttps://computing.llnl.gov/linux/slurm/cons_res_share.html\fR.
Possible values for \fBShared\fR are "EXCLUSIVE", "FORCE", "YES", and "NO".
.RS
.TP 12
\fBEXCLUSIVE\fR
Aallocates entire nodes to jobs even with select/cons_res configured.
This can be used to allocate whole nodes in some partitions
This can be used to allocate whole nodes in some partitions
and individual processors in other partitions.
and individual processors in other partitions.
"FORCE" makes all resources in the partition available for sharing
.TP
without user means of disabling it.
\fBFORCE\fR
"YES" makes nodes in the partition available for sharing if and
Make all resources in the partition available for sharing
only if the individual jobs permit sharing (see the srun
without any means for users to disable it.
"\-\-share" option).
May be followed with a colon and maximum number of jobs in
"NO" makes nodes unavailable for sharing under all circumstances.
running or suspended state.
The default value is "NO".
For example "Shared=FORCE:4" enables each node, socket or
The "FORCE" and "YES" options can be followed by a colon and a job
count. For example "Shared=YES:4" enables each node, socket or
core to execute up to four jobs at once.
core to execute up to four jobs at once.
If resources are to be shared, avoiding memory over\-subscription
Recommended only for BlueGene systems configured with
is very important.
small blocks or for systems running
With sched/gang this count is the maximum number of jobs permitted
with gang scheduling (\fBSchedulerType=sched/gang\fR).
on each resource in either running or suspended state (i.e. the total
.TP
number of jobs being time sliced).
\fBYES\fR
With other schedulers, this count is the maximum number of running
Make nodes in the partition available for sharing, but provides
jobs on each resource (node, socket or core depending upon the
the user with a means of getting dediated resources.
\fBSelectTypeParameters\fR).
If \fBSelectType=select/cons_res\fR, then resources will be
\fBSelectTypeParameters\fR should be configured to treat
over\-subscribed unless explicitly disabled in the job submit
memory as a consumable resource and the \fB\-\-mem\fR option
request using the "\-\-exclusive" option.
should be used for job allocations.
With \fBSelectType=select/bluegene\fR or \fBSelectType=select/linear\fR,
resources will only be over\-subscribed when explicitly requested
by the user using the "\-\-share" option on job submission.
May be followed with a colon and maximum number of jobs in
running or suspended state.
For example "Shared=YES:4" enables each node, socket or
core to execute up to four jobs at once.
Recommended only for systems running with gang scheduling
(\fBSchedulerType=sched/gang\fR).
.RE
.TP
.TP
\fBState\fR
\fBState\fR
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment