Caching of communicators
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.
An alternative scheme requires managing tags in the library more closely and is potentially less resource intensive (depending on how costly a communicator is).
Updated by Thomas Jahns over 6 years ago
- Assignee set to Thomas Jahns
- Status changed from New to Resolved
Management of tags is included since commit:d81df00949be65e4e83f21d36a2b548542fba677 and can be considered mature for some releases now. Thus this issue is resolved.