YAXT: Issueshttps://swprojects.dkrz.de/redmine/https://swprojects.dkrz.de/redmine/redmine/favicon.ico?17095821032015-04-24T13:13:20ZDKRZ projects
Redmine Task #336 (New): Compare performance of YAXT and other coupling middlewarehttps://swprojects.dkrz.de/redmine/issues/3362015-04-24T13:13:20ZThomas Jahnsjahns@dkrz.de
<p>The following projects deliver partially similar functionality and should be investigated for relative performance:</p>
<ul>
<li>MCT</li>
<li>ESMF</li>
</ul> Task #332 (Closed): allow empty messages in exchange routineshttps://swprojects.dkrz.de/redmine/issues/3322014-07-31T12:42:24ZJoerg Behrensbehrens@dkrz.de
<p>redists should be able to pass emtpy messages (struct Xt_redist_msg; with datatype = MPI_DATATYPE_NULL and rank = -1) to exchange routines.</p>
<p>These messages are just "place-holders" and should not trigger an actual exchange.</p>
<p>This should result in simple but general exchange routines that supports various message orders.</p> Task #316 (Closed): check if base redist class makes sensehttps://swprojects.dkrz.de/redmine/issues/3162013-03-08T16:47:22ZJoerg Behrensbehrens@dkrz.de
<p>if there is enough common functionality within the current redist variations then we should derive them from a base class</p>