You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I found that there is a discrepancy between the message size that the OSU benchmarks report and the size that is used by coll/tuned to make tuning decisions: the OSU benchmarks report the size of the message each rank sends while coll/tuned bases it's decision in allgatherv on the total amount of data to be received. This leads to nonsensical rules and likely suboptimal decisions. This should be fixed in the python scripts (when generating the decision file and ideally also when writing the best.out file).
The text was updated successfully, but these errors were encountered:
I found that there is a discrepancy between the message size that the OSU benchmarks report and the size that is used by
coll/tuned
to make tuning decisions: the OSU benchmarks report the size of the message each rank sends whilecoll/tuned
bases it's decision inallgatherv
on the total amount of data to be received. This leads to nonsensical rules and likely suboptimal decisions. This should be fixed in the python scripts (when generating the decision file and ideally also when writing thebest.out
file).The text was updated successfully, but these errors were encountered: