-
Notifications
You must be signed in to change notification settings - Fork 6
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
Trace: comm_summary and comm_over_time #91
Conversation
hsirkar
commented
Apr 5, 2023
•
edited
Loading
edited
- comm_summary computes total message count/volume sent and received per process
- comm_over_time computes total message count/volume sent over time
comm_matrix = self.comm_matrix(output=output) | ||
|
||
# Get total sent and received for each process | ||
sent = comm_matrix.sum(axis=1) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I recall a recent discussion about sends and receives being on the incorrect axes. Is this line related to that? Are we certain this is correct?
pipit/trace.py
Outdated
# Filter by send or receive events | ||
events = self.events[ | ||
self.events["Name"].isin( | ||
["MpiSend", "MpiIsend"] if kind == "send" else ["MpiRecv", "MpiIrecv"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is the naming always "MpiSend", or can it occasionally be written as "MPISend"? Do we need to handle that?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess it should be the same in all the readers so it shouldn't be a problem.
We need to think about why we have an additional "MPISend" event within the "MPI_Send" event and if we can remove it. |
ea66ae8
to
f2e9228
Compare