MPI profiling for hanging code
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 112
- Forks
- 35
- PR merge metrics
- No merged PRs in 30d
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.
Contributor guide
No contributing guide indexed for this repository
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.
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.
Assessment
- Tech stack
- c
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100