| |
| |
2.4 Agglomeration |
 | | In particular, we consider whether it is useful to combine, or agglomerate, tasks identified by the partitioning phase, so as to provide a smaller number of tasks, each of greater size (Figure 2.11). |
| | Agglomeration is almost always beneficial if analysis of communication requirements reveals that a set of tasks cannot execute concurrently. |
| | Alternatively, we may have used agglomeration to increase computation and communication granularity and/or to decrease software engineering costs, even though opportunities for concurrent execution are reduced. |
| www.mcs.anl.gov /dbpp/text/node18.html (2554 words) |
|
