llnl / llnl/mpiP

No mpiP report generated

Open
#31 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
112
Forks
35
PR merge metrics
No merged PRs in 30d

Description

Hi, I am using mpiP 3.5.0 to do profiling for [WRFV-3.9.1.1](https://github.com/NCAR/WRFV3/releases/tag/V3.9.1.1). I built mpiP with [Open MPI 4.0.5](https://www.open-mpi.org/software/ompi/v4.0/)
```
./configure --prefix=$MPIP_ROOT --disable-libunwind CC=/path/to/mpicc CXX=/path/to/mpicxx F77=/path/to/mpif77
```

and pre-load it in my mpirun as

```
mpirun -x "LD_PRELOAD=/path/to/libmpiP.so" ....(other mpi arguments) wrf.exe
```

I can see mpiP printed in the stdout as

```
mpiP:
mpiP: mpiP V3.5.0 (Build Dec 18 2020/00:20:30)
mpiP:
```

But there is no final report generated and no error message was printed. Could you help provide any suggestions on debugging this issue? The application is coded with fortran 90. But I used mpiP to do profiling for the simple mpif90 program [ring_usempi](https://github.com/open-mpi/ompi/blob/master/examples/ring_usempi.f90) and do not have such issue.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Compare the WRFV-3.9.1.1 launch with the working ring_usempi.f90 run, starting from the mpiP 3.5.0 output and the LD_PRELOAD setup in mpirun. Check the Open MPI 4.0.5 configuration and determine why no final report is produced; done when the cause is reproducible or a report is generated.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, fortran
Domain
performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.