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
One appealing feature of coarrays is the one-sided nature of the communication among images, allowing overlap of communication and computation. OpenCoarrays exploits this by using RMA functions and shared memory windows in MPI 3.
It would be interesting to measure what benefit ICAR sees in using one-sided communication via coarrays, over the traditional two-sided MPI communication which has been the standard programming model for bulk-synchronous parallel applications for many years. We can measure this by writing an analogous two-sided MPI version of ICAR and comparing the performance with the coarray version.
The text was updated successfully, but these errors were encountered:
@bcfriesen Cranfield University Ph.D. student Soren Rasmussen (@scrasmussen) has agreed to work this issue starting this week. He just arrived for a one-week visit at the worldwide headquarters of Sourcery Institute. :) If you've already done anything this, please let us know. Otherwise, he'll create a new branch and start working toward having this written up in time for the July 31 PAW-ATM workshop deadline.
One appealing feature of coarrays is the one-sided nature of the communication among images, allowing overlap of communication and computation. OpenCoarrays exploits this by using RMA functions and shared memory windows in MPI 3.
It would be interesting to measure what benefit ICAR sees in using one-sided communication via coarrays, over the traditional two-sided MPI communication which has been the standard programming model for bulk-synchronous parallel applications for many years. We can measure this by writing an analogous two-sided MPI version of ICAR and comparing the performance with the coarray version.
The text was updated successfully, but these errors were encountered: