Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
M
mpi-lab-exercises
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
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
GitLab community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
pdc-summer-school
mpi-lab-exercises
Commits
d0487f49
Commit
d0487f49
authored
5 years ago
by
Xin Li
Browse files
Options
Downloads
Patches
Plain Diff
aprun -> srun
parent
a8c3a798
No related branches found
No related tags found
No related merge requests found
Changes
2
Show whitespace changes
Inline
Side-by-side
Showing
2 changed files
README.md
+3
-3
3 additions, 3 deletions
README.md
lab3/README.md
+4
-2
4 additions, 2 deletions
lab3/README.md
with
7 additions
and
5 deletions
README.md
+
3
−
3
View file @
d0487f49
...
...
@@ -32,15 +32,15 @@ First it is necessary to book a node for interactive use:
salloc -A <allocation-name> -N 1 -t 1:0:0
```
Then the
ap
run command is used to launch an MPI application:
Then the
s
run command is used to launch an MPI application:
```
ap
run -n 32 ./example.x
s
run -n 32 ./example.x
```
In this example we will start 32 MPI tasks (there are 32 cores per node on the Beskow nodes).
If you do not use
ap
run and try to start your program on the login node then you will get an error similar to
If you do not use
s
run and try to start your program on the login node then you will get an error similar to
```
Fatal error in MPI_Init: Other MPI error, error stack:
...
...
This diff is collapsed.
Click to expand it.
lab3/README.md
+
4
−
2
View file @
d0487f49
...
...
@@ -56,13 +56,15 @@ Use `mpi_wtime` to compute latency and bandwidth with the bandwidth and latency
For this exercise, it is nice to compare running on the same node e.g.
```
aprun -n 2 ./mpi_latency.x
salloc -N 1 --ntasks-per-node=2 -A <project> -t 00:05:00
srun -n 2 ./mpi_latency.x
```
with running on separate nodes
```
aprun -N 1 -n 2 ./mpi_latency.x
salloc -N 2 --ntasks-per-node=1 -A <project> -t 00:05:00
srun -n 2 ./mpi_latency.x
```
Similarly for the bandwidth.
...
...
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