Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
docs.it4i.cz
Manage
Activity
Members
Labels
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container registry
Model registry
Operate
Environments
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
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
SCS
docs.it4i.cz
Commits
db262503
Commit
db262503
authored
1 month ago
by
Branislav Jansik
Browse files
Options
Downloads
Patches
Plain Diff
Edit capacity-computing.md
parent
af5d7f62
Branches
Branches containing commit
Tags
Tags containing commit
No related merge requests found
Pipeline
#44111
failed
1 month ago
Stage: test
Stage: build
Stage: deploy
Stage: after_test
Changes
1
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs.it4i/general/capacity-computing.md
+4
-3
4 additions, 3 deletions
docs.it4i/general/capacity-computing.md
with
4 additions
and
3 deletions
docs.it4i/general/capacity-computing.md
+
4
−
3
View file @
db262503
...
@@ -8,15 +8,16 @@ achieving the best runtime, throughput, and computer utilization. This is called
...
@@ -8,15 +8,16 @@ achieving the best runtime, throughput, and computer utilization. This is called
However, executing a huge number of jobs via the Slurm queue may strain the system. This strain may
However, executing a huge number of jobs via the Slurm queue may strain the system. This strain may
result in slow response to commands, inefficient scheduling, and overall degradation of performance
result in slow response to commands, inefficient scheduling, and overall degradation of performance
and user experience for all users. We
**recommend**
using
[
**Job arrays**
][
1
]
or
[
**HyperQueue**
][
2
]
to execute many jobs.
and user experience for all users.
We
**recommend**
using
[
**Job arrays**
][
1
]
or
[
**HyperQueue**
][
2
]
to execute many jobs.
There are two primary scenarios:
There are two primary scenarios:
1.
Numeber of jobs < 1500,
**and**
the jobs are able to utilize one or more full nodes:
1.
Numeber of jobs < 1500,
**and**
the jobs are able to utilize one or more
**
full
**
nodes:
Use
[
**Job arrays**
][
2
]
.
Use
[
**Job arrays**
][
2
]
.
The Job array allows to sumbmit and control many jobs (tasks) in one packet. Several job arrays may be sumitted.
The Job array allows to sumbmit and control many jobs (tasks) in one packet. Several job arrays may be sumitted.
2.
Number of jobs >> 1500,
**or**
the jobs only utilze a few cores each:
2.
Number of jobs >> 1500,
**or**
the jobs only utilze a
**
few cores
/accelerators**
each:
Use
[
**HyperQueue**
][
1
]
.
Use
[
**HyperQueue**
][
1
]
.
HyperQueue can help efficiently load balance a very large number of (small) jobs amongst available computing nodes.
HyperQueue can help efficiently load balance a very large number of (small) jobs amongst available computing nodes.
HyperQueue may be also used if you have dependenices among the jobs.
HyperQueue may be also used if you have dependenices among the jobs.
...
...
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