Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
hpc-compendium
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor 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
ZIH
hpcsupport
hpc-compendium
Commits
4bd5847d
Commit
4bd5847d
authored
1 year ago
by
Natalie Breidenbach
Browse files
Options
Downloads
Patches
Plain Diff
Update mpi_issues.md
parent
7586bddd
No related branches found
No related tags found
2 merge requests
!938
Automated merge from preview to main
,
!936
Update to Five-Cluster-Operation
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc.zih.tu-dresden.de/docs/jobs_and_resources/mpi_issues.md
+3
-3
3 additions, 3 deletions
doc.zih.tu-dresden.de/docs/jobs_and_resources/mpi_issues.md
with
3 additions
and
3 deletions
doc.zih.tu-dresden.de/docs/jobs_and_resources/mpi_issues.md
+
3
−
3
View file @
4bd5847d
...
@@ -30,9 +30,9 @@ or setting the option as argument, in case you invoke `mpirun` directly
...
@@ -30,9 +30,9 @@ or setting the option as argument, in case you invoke `mpirun` directly
marie@login$
mpirun
--mca
io ^ompio
[
...]
marie@login$
mpirun
--mca
io ^ompio
[
...]
```
```
### Mpirun on
Partition
s `alpha` and `
ml
`
### Mpirun on
cluster
s `alpha` and `
power
`
<!-- laut max möglich dass es nach dem update von alpha und power9 das problem nicht mehr relevant ist.-->
Using
`mpirun`
on
partition
s
`alpha`
and
`
ml
`
leads to wrong resource distribution when more than
Using
`mpirun`
on
cluster
s
`alpha`
and
`
power
`
leads to wrong resource distribution when more than
one node is involved. This yields a strange distribution like e.g.
`SLURM_NTASKS_PER_NODE=15,1`
one node is involved. This yields a strange distribution like e.g.
`SLURM_NTASKS_PER_NODE=15,1`
even though
`--tasks-per-node=8`
was specified. Unless you really know what you're doing (e.g.
even though
`--tasks-per-node=8`
was specified. Unless you really know what you're doing (e.g.
use rank pinning via perl script), avoid using mpirun.
use rank pinning via perl script), avoid using mpirun.
...
...
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