YAXT: Issues https://www.dkrz.de/redmine https://www.dkrz.de/redmine/redmine/favicon.ico?1571477570 2014-08-06T16:29:45Z DKRZ projects Redmine Feature #333 (Resolved): Caching of communicators https://www.dkrz.de/redmine/issues/333 2014-08-06T16:29:45Z Thomas Jahns jahns@dkrz.de <p>YAXT currently creates communicators internally to provide isolation from other parts of the system. This can be potentially costly when it introduces additional synchronization. For this reason it seems sensible to cache previously created communicators instead of destroying them immediately.</p> <p>An alternative scheme requires managing tags in the library more closely and is potentially less resource intensive (depending on how costly a communicator is).</p> Feature #311 (Resolved): stripify xt_xmap_dist_dir_new https://www.dkrz.de/redmine/issues/311 2012-11-26T15:24:20Z Joerg Behrens behrens@dkrz.de <p>Following the idea of using bounding boxes for xmap constructions we could consider to implement a stripe-set form of all involved ingredients.<br />This avoids vectorization to death of big compact index lists (better scalability). This is suitable for a one-dim distributed directory which might not scale perfectly but probably is more cost effective for medium sized problems.</p>