Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
D
Documentation
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container 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
PathoJobs
Documentation
Wiki
Unnecessary job distribution
Changes
Page history
New page
Templates
Clone repository
Create Unnecessary job distribution
authored
1 year ago
by
Alex Wiens
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
Unnecessary-job-distribution.md
+15
-0
15 additions, 0 deletions
Unnecessary-job-distribution.md
with
15 additions
and
0 deletions
Unnecessary-job-distribution.md
0 → 100644
View page @
13ea79dc
*
Description:
Job distributes tasks over multiple nodes even if they fit one node.
This might lead to increased communication latency and redundant network traffic when reading from filesystems.
*
Criterion:
Number of allocated cores fit one node.
Additional criterion: High I/O or Lustre Bandwidth indicates high communication overhead (possibly unreliable metric on shared nodes).
Possibly, check SLURM arguments.
*
Possible false positives:
MPI distributed program uses multiple accelerators and scheduler allocates accelerators on different nodes.
Program actually benefits from multiples nodes since it uses a lot of memory bandwidth.
*
Possible cures/workarounds: Use -N to specify number of nodes.
Use --contiguous to use contiguous resources.
This diff is collapsed.
Click to expand it.