-
Notifications
You must be signed in to change notification settings - Fork 1
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
#269: added printing and calculating statistics from sub-phases #276
#269: added printing and calculating statistics from sub-phases #276
Conversation
@ppebay Philippe please take a look if what I have done make sense. Best would be to try with |
It looks like there was a small mis-communication of what we were looking for. We primarily want the statistics computed and reported for each subphase, not sums over all of them. Once we have that, then we can start doing comparisons between what an aggregate of the subphases shows and what's seen for the entire phase. |
@marcinwrobel1986 are we ready to review this PR? |
We will be tomorrow. |
- added compute_subphases to work models - added printing statistics from sub-phases in algorithms and main LBAF routine - added get_subphases_time to object - added printing statistics from sub-phases when populating from log - fixed returned type for is_sentinel in Rank
feede4d
to
70cd6fc
Compare
@marcinwrobel1986 is this PR ready for review? |
@ppebay this is calculating the load from subphases, but all the subphases. This part is finished and ready for review and to be merged. In current situation it would be a good idea to merge that and create another issue, with proper description that Phil created, where one would implement statistics computed and reported for each subphase. Below is Phil's comment:
|
Computing a summed load across all of the subphases is not especially useful functionality. The point is to do the subphase-sensitive calculations that would let us apply reasoning as described in this report: https://github.com/DARMA-tasking/vector-balancing-report |
@PhilMiller I agree. Should we nevertheless merge this current PR -- or discard it altogether, as the summation across all subphases is not useful? |
Discard it, or fix it to do the useful things. |
Discarding this PR that is not doing what is needed |
closes #269