User:Kortasch/Collective operation

Collective operations are building blocks for interaction patterns, that are often used in SPMD algorithms in the parallel programming context. Hence, there is an interest in efficient realizations of these operations.

A realization of the collective operations is provided by the Message Passing Interface (MPI).

Definitions
In all asymptotic runtime functions, we denote the latency $$\alpha$$, the communication cost per word $$\beta$$, the number of processing units $$p$$ and the input size per node $$n$$. In cases where we have initial messages on more than one node we assume that all local messages are of the same size. To address individual processing units we use $$p_i \in \{ p_0, p_1, \dots, p_{p - 1} \}$$.

If we do not have an equal distribution, i.e. node $$p_i$$ has a message of size $$n_i$$, we get an upper bound for the runtime by setting $$n = \max(n_0, n_1, \dots, n_{p-1})$$.

A distributed memory model is assumed. The concepts are similar for the shared memory model. However, shared memory systems can provide hardware support for some operations like broadcast for example, which allows convenient concurrent read. Thus, new algorithmic possibilities can become available.

Broadcast


The broadcast pattern is used to distribute data from one processing unit to all processing units, which is often needed in SPMD parallel programs to dispense input or global values. Broadcast can be interpreted as an inverse version of the reduce pattern. Initially only root $$r$$ with $$id$$ $$0$$ stores message $$m$$. During broadcast $$m$$ is sent to the remaining processing units, so that eventually $$m$$ is available to all processing units.

Since an implementation by means of a sequential for-loop with $$p-1$$ iterations becomes a bottleneck, divide-and-conquer approaches are common. One possibility is to utilize a binomial tree structure with the requirement that $$p$$ has to be a power of two. When a processing unit is responsible for sending $$m$$ to processing units $$i..j$$, it sends $$m$$ to processing unit $$\left \lceil (i+j)/2 \right \rceil$$ and delegates responsibility for the processing units $$\left \lceil (i+j)/2 \right \rceil .. \left \lceil (i+j)-1 \right \rceil$$ to it, while its own responsibility is cut down to $$i..\left \lceil (i+j)/2 \right \rceil-1$$.

Binomial trees have a problem with long messages $$m$$. The receiving unit of $$m$$ can only propagate the message to other units, after it received the whole message. In the meantime, the communication network is not utilized. Therefore pipelining on binary trees is used, where $$m$$ is split into an array of $$k$$ packets of size $$\left \lceil n/k \right \rceil $$. The packets are then broadcasted one after another, so that data is distributed fast in the communication network.

Pipelined broadcast on balanced binary tree is possible in $$\mathcal{O}(\alpha \log p + \beta n)$$.

Reduce


The reduce pattern is used to collect data or partial results from different processing units and to combine them into a global result by a chosen operator. Reduction can be seen as an inverse version of broadcast. Given $$p$$ processing units, message $$m_i$$ is on processing unit $$p_i$$ initially. All $$m_i$$ are aggregated by $$\otimes$$ and the result is eventually stored on $$p_0$$. The reduction operator $$\otimes$$ must be associative at least. Some algorithms require a commutative operator with a neutral element. Operators like $$sum$$, $$min$$, $$max$$ are common.

Since reduce can be interpreted as an inverse broadcast, equal implementation considerations apply. For pipelining on binary trees the message must be representable as a vector of smaller object for component-wise reduction.

Pipelined reduce on a balanced binary tree is possible in $$\mathcal{O}(\alpha \log p + \beta n)$$.

All-Reduce


The all-reduce pattern is used, if the result of a reduce operation must be distributed to all processing units. Given $$p$$ processing units, message $$m_i$$ is on processing unit $$p_i$$ initially. All $$m_i$$ are aggregated by an operator $$\otimes$$ and the result is eventually stored on all $$p_i$$. Analog to the reduce operation, the operator $$\otimes$$ must be at least associative.

All-reduce can be interpreted as a reduce operation with a subsequent broadcast. For long messages a corresponding implementation is suitable, whereas for short messages, the latency can be reduced by using a hypercube topology, if $$p$$ is a power of two.

All-reduce is possible in $$\mathcal{O}(\alpha \log p + \beta n)$$, since reduce and broadcast are possible in $$\mathcal{O}(\alpha \log p + \beta n)$$ with pipelining on balanced binary trees.

Prefix-Sum/Scan


The prefix-sum or scan operation is used to collect data or partial results from different processing units and to compute intermediate results by an operator, which are stored on those processing units. It can be seen as a generalization of the reduce operation. Given $$p$$ processing units, message $$m_i$$ is on processing unit $$p_i$$. The operator $$\otimes$$ must be at least associative, whereas some algorithms require also a commutative operator and a neutral element. Common operators are $$sum$$, $$min$$ and $$max$$. Eventually processing unit $$p_i$$ stores the prefix sum $$\otimes_{i' <= i}$$$$m_{i'}$$. In the case of the so-called exclusive prefix sum, processing unit $$p_i$$ stores the prefix sum $$\otimes_{i' < i}$$$$m_{i'}$$. Some algorithms require to store the overall sum at each processing unit in addition to the prefix sums.

For short messages, this can be achieved with a hypercube topology if $$p$$ is a power of two. For long messages, the hypercube topology is not suitable, since all processing units are active in every step and therefore pipelining can't be used. A binary tree topology is better suited for arbitrary $$p$$ and long messages.

Prefix-sum on a binary tree can be implemented with an upward and downward phase. In the upward phase reduction is performed, while the downward phase is similar to broadcast, where the prefix sums are computed by sending different data to the left and right children. With this approach pipelining is possible, because the operations are equal to reduction and broadcast.

Pipelined prefix sum on a binary tree is possible in $$\mathcal{O}(\alpha \log p + \beta n)$$.

Barrier
The barrier as a collective operation is a generalization of the concept of a barrier, that can be used in distributed computing. When a processing unit calls barrier, it waits until all other processing units have called barrier as well. Barrier is thus used to achieve global synchronization in distributed computing.

One way to implement barrier is to call all-reduce with an empty/ dummy operand. We know the runtime of All-reduce is $$ \mathcal{O}(\alpha \log p + \beta n) $$. Using a dummy operand reduces size $$n$$ to a constant factor and leads to a runtime of $$\mathcal{O}(\alpha \log p)$$.

Gather


The gather communication pattern is used to store data from all processing units on a single processing unit. Given $$p$$ processing units, message $$m_i$$ on processing unit $$p_i$$. For a fixed processing unit $$p_j$$, we want to store the message $$m_1 \cdot m_2 \cdot \ldots \cdot m_p$$ on $$p_j$$. Gather can be thought of as a reduce operation that uses the concatenation operator. This works due to the fact that concatenation is associative. By using the same binomial tree reduction algorithm we get a runtime of $$\mathcal{O}(\alpha \log p + \beta p n)$$. We see that the asymptotic runtime is similar to the asymptotic runtime of reduce $$\mathcal{O}(\alpha \log p + \beta n)$$, but with the addition of a factor p to the term $$\beta n$$. This additional factor is due to the message size increasing in each step as messages get concatenated. Compare this to reduce where message size is a constant for operators like $$min$$.

All-Gather


The all-gather communication pattern is used to collect data from all processing units and to store the collected data on all processing units. Given $$p$$ processing units $$p_i$$, message $$m_i$$ initially stored on $$p_i$$, we want to store the message $$m_1 \cdot m_2 \cdot \ldots \cdot m_p$$ on each $$p_j$$.

It can be thought of in multiple ways. The first is as an all-reduce operation with concatenation as the operator, in the same way that gather can be represented by reduce. The second is as a gather-operation followed by a broadcast of the new message of size $$pn$$. With this we see that all-gather in $$\mathcal{O}(\alpha \log p + \beta p n)$$ is possible.

Scatter


The scatter communication pattern is used to distribute data from one processing unit to all the processing units. It differs from broadcast, in that it does not send the same message to all processing units. Instead it splits the message and delivers one part of it to each processing unit.

Given $$p$$ processing units $$p_i$$, a fixed processing unit $$p_j$$ that holds the message $$m = m_1 \cdot m_2 \cdot \ldots \cdot m_p$$. We want to transport the message $$m_i$$ onto $$p_i$$. The same implementation concerns as for gather apply. This leads to an optimal runtime in $$\mathcal{O}(\alpha \log p + \beta p n)$$.

All-to-all
All-to-all is the most general communication pattern. For $$0 \leq i < p, 0 \leq j < p$$, message $$m_{i, j}$$ is the message that is initially stored on node $$i$$ and has to be delivered to node $$j$$. We can express all communication primitives that do not use operators through all-to-all. For example, broadcast of message $$m$$ from node $$p_k$$ is emulated by setting $$m_{i, j} = m$$ for $$i = k$$ and setting $$m_{l, j}$$ empty for $$l \neq k$$.

Assuming we have a fully connected network, the best possible runtime for all-to-all is in $$\mathcal{O}(p (\alpha + \beta n))$$. This is achieved through $$p$$ rounds of direct message exchange. For $$p$$ power of 2, in communication round $$k$$, node $$p_i$$ exchanges messages with node $$p_j, j = i \oplus k$$.

If the message size is small and latency dominates the communication, a hypercube algorithm can be used to distribute the messages in time $$\mathcal{O}(\log p (\alpha + \beta p n))$$.

Runtime Overview
This table gives an overview over the best known asymptotic runtimes, assuming we have free choice of network topology.

Example topologies we want for optimal runtime are binary tree, binomial tree, hypercube.

In practice, we have to adjust to the available physical topologies, e.g. dragonfly, fat tree,  grid network (references other topologies, too).

More information under Network topology.

For each operation, the optimal algorithm can depend on the input sizes $$n$$. For example, broadcast for short messages is best implemented using a binomial tree whereas for long messages a pipelined communication on a balanced binary tree is optimal.

The complexities stated in the table depend on the latency $$\alpha$$ and the communication cost per word $$\beta$$ in addition to the number of processing units $$p$$ and the input message size per node $$n$$. The # senders and # receivers columns represent the number of senders and receivers that are involved in the operation respectively. The # messages column lists the number of input messages and the Computations? column indicates if any computations are done on the messages or if the messages are just delivered without processing. Complexity gives the asymptotic runtime complexity of an optimal implementation under free choice of topology.

TODO:
Add ref from Parallel algorithm

Distributed algorithm (ref to or from?)

Deutscher Wiki-Artikel zu MPI enthält manche Algorithmen