Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

mpiP profiling data problem

Open
#37 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
c
Domain
performance

Research direction

Start by reviewing mpiP's profiling data and the callSite property mentioned in the issue. Determine whether MPI rank, function names, source and destination, message size, and start and end times are currently available; done requires a clear capability or implementation scope for the requested trace data.

Written by the indexing model from the issue text.

Description

Hi,

The mpiP profiling data has a callSite property, I did not understand it.

I want to collect mpi trace data like this:
MPI_RANK {MPI_Functionlist} such as process 0 : {MPI_send, MPI_rev, ……}
and How can I know the source and destination of each MPI function call, along with the message_size and start_time, end_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

  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.

More from llnl/mpiP

All issues in llnl/mpiP

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.