Project

General

Profile

Bug #635

all trees should be pe/node/physnode/network topology aware

Added by Jim Phillips over 4 years ago. Updated almost 2 years ago.

Status:
Merged
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
12/19/2014
Due date:
% Done:

0%


Description

There are various places in Charm++ where broadcast and reduction trees are implemented as PE n to PEs 2*n+1 and 2*n+2 (or the obvious k-way extension). These should in all instances be replaced with a standard tree that aggregates communication hierarchically within a PE, node, physical node, and finally whatever network topology can be detected. It doesn't need to be perfect at first, but we do need a single tree-generating utility that can be called everywhere that this kind of tree is needed.


Related issues

Related to Charm++ - Feature #1494: Broadcast trees are not topology-aware Merged 04/10/2017
Related to Charm++ - Bug #1278: ReductionStarting overhead in SMP mode Merged 11/02/2016

History

#1 Updated by Nikhil Jain over 3 years ago

  • Target version changed from 6.7.0 to 6.7.1

#2 Updated by Nikhil Jain over 3 years ago

  • Assignee set to Juan Galvez

#3 Updated by Sam White over 3 years ago

  • Target version changed from 6.7.1 to 6.8.0

#4 Updated by Phil Miller over 2 years ago

  • Related to Feature #1494: Broadcast trees are not topology-aware added

#5 Updated by Phil Miller about 2 years ago

  • Related to Bug #1278: ReductionStarting overhead in SMP mode added

#6 Updated by Phil Miller about 2 years ago

Reductions are now at least SMP aware due to the fix for #1278. We still form a topology-oblivious tree over the nodes, though.

#7 Updated by Phil Miller about 2 years ago

  • Tracker changed from Cleanup to Bug

This is a potentially serious performance defect, not just something to tidy up.

#8 Updated by Phil Miller about 2 years ago

  • Target version changed from 6.8.0 to 6.8.1

#9 Updated by Juan Galvez about 2 years ago

  • Status changed from New to In Progress

#11 Updated by Phil Miller almost 2 years ago

  • Status changed from Implemented to Merged

Also available in: Atom PDF