Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pure-MPI implementation in a Podman container #203

Merged
merged 37 commits into from
Dec 31, 2024
Merged

pure-MPI implementation in a Podman container #203

merged 37 commits into from
Dec 31, 2024

Conversation

moustakas
Copy link
Member

This PR implements a pure-MPI version of FastSpecFit, which does not make use of multiprocessing at all. In addition, a given production (e.g., Y3/Loa) can be run entirely out of a Podman container, which gives us full control over the input software stack (see here for details, including the instructions file).

In production, parallelism is controlled by bin/mpi-fastspecfit. The number of MPI tasks in the mpi4py.MPI.COMM_WORLD communicator (as given by srun --ntasks=n) is split into int(ceil(n/mp)) sub-communicators, where mp is the number of desired ranks per sub-communicator. Using the rank=0 ranks in the sub-communicators, we parallelize over healpixels; in addition, all the ranks in a given sub-communicator are used to parallelize over objects / targets in fastspecfit.fastspec(). In particular, in fastspecfit.fastspec() we use comm.send and comm.recv (send and receive) to make sure each rank only sees the data it needs, which should help prevent memory overflow problems.

I'll post timing tests shortly. And at the moment, there is one issue that I have not been able to track down, but perhaps others may have some ideas.

@moustakas moustakas merged commit 42bf09d into main Dec 31, 2024
14 of 16 checks passed
@moustakas moustakas deleted the pure-MPI branch December 31, 2024 14:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant