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
b9fdd2a1
Commit
b9fdd2a1
authored
7 years ago
by
Morris Jette
Browse files
Options
Downloads
Patches
Plain Diff
Update heterogeneous job web page with respect to limits
parent
058b99b6
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/html/heterogeneous_jobs.shtml
+17
-11
17 additions, 11 deletions
doc/html/heterogeneous_jobs.shtml
with
17 additions
and
11 deletions
doc/html/heterogeneous_jobs.shtml
+
17
−
11
View file @
b9fdd2a1
...
...
@@ -392,17 +392,23 @@ mode is used in the next iteration in order to consider system status changes
which might permit the heterogeneous to be initiated at an earlier time than
previously determined.</p>
<p>There is currently no test performed at job submit time to determine if all
components of a heterogeneous job can be started at the same time with respect
to account and quality of service (QOS) limits.
Each component will be validated to be executable at job submit time and the
heterogeneous job as a whole will only be validated with respect to limits
when being considered for resource allocation (i.e. scheduling time).</p>
<p>A resource limit test is performed when a heterogeneous job is submitted in
order to immediately reject jobs that will not be able to start with current
limits.
The individual components of the heterogeneous job are validated, like all
regular jobs.
The heterogeneous job as a whole is also tested, but in a more limited
fashion with respect to quality of service (QOS) limits.
This is due to the complexity of each job component having up to three sets of
limits (association, job QOS and partition QOS).
Note that successful submission of any job (heterogeneous or otherwise) does
not insure the job will be able to start without exceeding some limit.
For example a job's CPU limit test does not consider that CPUs might not be
allocated individually, but resource allocations might be performed by whole
core, socket or node.
Each component of a heterogeneous job counts as a "job" with respect to
resource limits.</p>
<p>Each component of a heterogeneous job counts as a "job" with respect to
resource limits.
Also note that a heterogeneous job may be submitted to Slurm that can not be
started with the current limits.
For example, a user might have a limit of 2 concurrent running jobs and submit
a heterogeneous job with 3 components.
Such a situation will have an adverse effect upon scheduling other jobs,
...
...
@@ -410,6 +416,6 @@ especially other heterogeneous jobs.</p>
<p class="footer"><a href="#top">top</a></p>
<p style="text-align:center;">Last modified 2
5
July 2017</p>
<p style="text-align:center;">Last modified 2
8
July 2017</p>
<!--#include virtual="footer.txt"-->
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