Daniel Kapla
1992c38dc4

11 months ago  

..  
images  11 months ago  
src  11 months ago  
README.md  11 months ago 
README.md
Lecture: 360.243 Numerical Simulation and Scientific Computing II, SS2022
Exercise 1
Handout: Thursday, March 10
Submission: Deadline for the group submission via TUWEL is Thursday, March 31, end of day

Include the name of all actively collaborated group members in the submission documents.

The binaries should be callable with command line parameters as specified below.

Submit everything (Makefiles, ShellScripts, Sources, Binaries, PDF with Plots/Discussion) as one zipfile per task.

TUWELCourse: https://tuwel.tuwien.ac.at/course/view.php?idnumber=3602432022S
General information

Use (and assume) the double precision floating point representation.

Test your MPIparallel implementation on your local machine before you benchmark on the cluster.

Compare the results (i.e., residual and error) with your serial implementation to ensure a correct implementation.

Use only a small number of Jacobi iterations when benchmarking the performance your code: convergence is not required during benchmarking.
MPIParallel StencilBased Jacobi Solver
In this exercise, your task is to parallelize a stencilbased Jacobi solver for the 2D elliptic PDE $$ \Delta u(x,y) + k^2 u(x,y) = f(x,y) \quad, \text{with} \ k=2\pi $$ for the "unit square" domain $$ \Omega = [0,1] \times [0,1] $$ with the analytic solution $$ u_p(x,y) = \sin(2\pi x) \sinh(2\pi y) $$ and righthandside $$ f(x,y) = k^2 u_p(x,y) $$ by implementing an MPIbased domain decomposition. The PDE is discretized on a regular finitedifference grid with fixed (Dirichlet) boundary conditions: $$ \begin{align} u(0,y) &= 0 \ u(1,y) &= 0 \ u(x,0) &= 0 \ u(x,1) &= \sin(2\pi x)\sinh(2\pi) \end{align} $$ The secondorder derivates are discretized using a central difference scheme resulting in a "5point starshaped stencil". As a staring point for your implementation, you can use your own serial implementation of the Jacobi solver from the NSSC I exercises or use the sourcecode distributed with this exercise (solver.hpp).
Domain Decomposition
Your task is to decompose the finitedifference grid into domain regions such that multiple MPIprocesses can independently perform an iteration on each region. The decoupling of the regions is achieved by introducing a ghost layer of grid points which surrounds each region. The values in the ghost layer of a region are not updated during an iteration.
Instead, after an iteration is finished the updated values for the ghost layer are received from the neighboring regions, and the boundary layer is sent to the neighboring regions (see Figure below).
Task 1: Questions (3 points)
 Describe the advantages/disadvantages of a twodimensional decomposition (compared to a onedimensional decomposition).
 Discuss if the decomposition of the domain changes the order of computations performed during a single Jacobi iteration (i.e., if you expect a numerically identical result after each iteration, or not).
 A generalization of the ghost layer approach would be to set the width of the ghost layer that is exchanged as a parameter
W
of the decomposition. This allows to performW
independent iterations before a communication of the ghost layers has to happen. Comment in which situation (w.r.t the available bandwidth or latency between MPIprocesses) multiple independent iterations are potentially advantageous.  Assume a ghost layer with width
W=1
(this is what you will later implement) and discuss if a data exchange between parts of the domain which are "diagonal neighbors" is required (assuming a "5point starshaped stencil").  How big is the sum of all L2 caches for 2 nodes of the IUEcluster link
Task 2: OneDimensional Decomposition (4 points)
Your task is to implement a onedimensional decomposition using a ghost layer and MPIcommunication to update the ghost layers. Create a program which is callable like this:
mpirun n NUMMPIPROC ./jacobiMPI resolution iterations
# example call
mpirun n 4 ./jacobiMPI 250 30
NUMMPIPROC
: number of MPIprocesses to launchresolution
: number of grid points along each dimension of the unit square; the grid spacing is $h = 1.0/(\text{resolution}1)
$iterations
: number of Jacobi iterations to perform
Further and more specifically, your program should
 use $
\bar{u}_h=\mathbf{0}
$ as initial approximation to $u
$, and (after finishing all iterations)  print the Euclidean $
\parallel \cdot \parallel_2
$ and Maximum $\parallel \cdot \parallel_{\infty}
$ norm of the residual $\parallel A_h\bar{u}_hb_h \parallel
$ and of the total error $\parallel \bar{u}_hu_p \parallel
$ to the console,  print the average run time per iteration to the console, and
 produce the same results as a serial run.
Finally, benchmark the parallel performance of your program jacobiMPI
using 2 nodes of the IUECluster for 4 different resolution
s=$\{125,250,1000,4000\}
$ using between 1 and 80 MPIprocesses (NUMMPIPROC
).
More specifically, you should
 create a plot of the parallel speedup and a plot of the parallel efficiency for each
resolution
, and  discuss your results in detail.
Notes:
 On your local machine, you can also launch MPIruns using mpirun (after installing MPI, see
Makefile
for install commands on Ubuntu)  An example of a ”MPI”Makefile and of a job submission script are provided with this exercise.
 The use of
MPI_Cart_create
,MPI_Cart_coords
, andMPI_ Cart_shift
for setup of the communication paths is recommended.  Your implementation should work for any positive integer supplied for
NUMMPIPROC
(e.g., 1,2,3,4,...) and also utilize this number of processes for the decomposition.
Task 3: TwoDimensional Decomposition (3 points)
Extend your program from Task 2 by implementing a twodimensional decomposition using a ghost layer and MPIcommunication to update the ghost layers. Create a program which is callable like this:
mpirun n NUMMPIPROC ./jacobiMPI DIM resolution iterations
# example call
mpirun n 4 ./jacobiMPI 2D 125 200
 the command line parameters have the same meaning as above in Task 2
 the new parameter
DIM
has two valid values1D
or2D
and switches between onedimensional and twodimensional decomposition.
Ensure a correct implementation by comparing your results to a serial run. Benchmarking on the cluster is not required.
Notes:
 Your implementation should work for any positive integer supplied for NUMMPIPROC (e.g., 1,2,3,4,...) and also utilize this number of processes for the 2D decomposition.
 If a the 2D composition is not possible with the supplied number of processes (i.e., a prime number), your program should resort to a 1D decomposition.
Working with the IUECluster
Connecting
 Your login credentials will be provided via email.
 You need to enable a "TU Wien VPN" connection.
 You can login to the cluster using
ssh
and your credentials.  You will be asked to change your initial password upon first login.
File Transfer
 You can checkout this gitRepository once you are connected to the cluster.
 You can transfer files and folders between your local machine and the cluster using
scp
 All nodes of the cluster operate on a shared file system (all your files on the cluster are also available when executing jobs)
Compiling on the cluster
 The cluster has a login node (the one you
ssh
to, details will be announced in the email with the credentials)  This login node must only be used to compile your project and never to perform any benchmarks or MPIruns (beside minimal lightweight tests of for the MPI configuration)
 All other nodes of the cluster are used to run the "jobs" you submit.
 To support cluster users, a set of environment modules (relevant for us is only the "MPI"module) is made available. You can list all modules using
module avail
 Note that you also need to load the modules you require in your job submission scripts (see example provided in this repo).
Executing jobs on the cluster
 Once you successfully compiled your program on the login node of the cluster, you are read to submit jobs.
 On our cluster job submissions are handled by the workload manager
SLURM
(a very common choice).  A job essentially is a shellscript which contains a call of your executable (see examples in this repo) A additionally a jobscript specifies its demands w.r.t. to resources, e.g.
 how many nodes are required?
 which runtime is anticipated?
 how many MPIprocesses should be launched on each node?
 After you submitted the job, it is up to the
SLURM
scheduler to queue it into the waiting list and to inform you once the job has completed.  The "results" of your job are
 Potential output files which your program produced during execution.
 The recording of the stdout and stderr which was recorded while your job executed (e.g.,
slurm12345.out
)
Useful Resources
SSH: https://phoenixnap.com/kb/sshtoconnecttoremoteserverlinuxorwindows
SCP: https://linuxize.com/post/howtousescpcommandtosecurelytransferfiles/
SLURM: https://slurm.schedmd.com/quickstart.html
Environment Modules: https://modules.readthedocs.io/en/latest/