MPI profiling for hanging code
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- c
- Domain
- performance
Research direction
No files, tests, or entry points are named in the issue. Start by locating where mpiP writes its report and how the application lifetime is observed, then assess a timed trigger for intermediate reports. Done means a hanging or long-running MPI program can produce a profile after the requested interval without waiting for normal completion.
Written by the indexing model from the issue text.
Description
mpiP generates the profile if a program ends completely. Is it possible to generate the profile after some time as many codes either never completes (generate intermediate files) or have some programming issues. This would be helpful to debug the slow/hung applications to identify what communication operations were used and in what message range. A simple environment variable might be implemented to trigger the writing of the mpiP report at some specified time.
- Dominant language
- C
- Stars
- 112
- Forks
- 35
- PR merge metrics
- No merged PRs in 30d
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from llnl/mpiP
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
-
MPI 4.0 SupportOpen
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Communication matrixOpen
Difficulty 4/5 3-5 days Newbie friendliness 30/100
-
ARM supportOpen
Difficulty 4/5 3-5 days Newbie friendliness 30/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
[Issue]: Headers - vx_ext_amd.h does not compile as C (enum types used without the enum keyword)Open
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Qiskit/qiskit#17079 · 1 comment ·
Maintainers usually reply within 1 day