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
1e838b58
Commit
1e838b58
authored
2 months ago
by
Branislav Jansik
Browse files
Options
Downloads
Patches
Plain Diff
Edit capacity-computing.md
parent
fb8fb4f7
Branches
Branches containing commit
No related tags found
No related merge requests found
Pipeline
#44103
failed
2 months 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
+11
-8
11 additions, 8 deletions
docs.it4i/general/capacity-computing.md
with
11 additions
and
8 deletions
docs.it4i/general/capacity-computing.md
+
11
−
8
View file @
1e838b58
...
@@ -2,20 +2,23 @@
...
@@ -2,20 +2,23 @@
## Introduction
## Introduction
In many cases, it is useful to submit a huge
(>100)
number of computational jobs into the Slurm queue system.
In many cases, it is useful to submit a huge number of computational jobs into the Slurm queue system.
A huge number of (small) jobs is one of the most effective ways to execute embarrassingly parallel calculations,
A huge number of (small) jobs is one of the most effective ways to execute embarrassingly parallel calculations,
achieving the best runtime, throughput, and computer utilization.
achieving the best runtime, throughput, and computer utilization.
This is called the
**Capacity Computing**
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.
and user experience for all users.
[
//
]:
#
(For this reason, the number of jobs is **limited
to
100 jobs per user, 4,000 jobs and subjobs per user, 1,500 subjobs per job array**.)
There are
t
w
o
primary scenarios:
!!! note
1.
Numeber of jobs < XXX, the jobs are able to utilize one or more full nodes
Follow one of the procedures below, in case you wish to schedule more than 100 jobs at a time
.
Use
[
Job arrays
][
2
]
.
You can use
[
HyperQueue
][
1
]
when running a huge number of jobs. HyperQueue can help efficiently
2.
Number of jobs >> XXX, the jobs only utilze few cores.
load balance a large number of jobs amongst available computing nodes.
Use
[
HyperQueue
][
1
]
when running a huge number of jobs. HyperQueue can help efficiently
load balance a large number of jobs amongst available computing nodes.
[
1
]:
hyperqueue.md
[
1
]:
job-arrays.md
[
2
]:
hyperqueue.md
\ No newline at end of file
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