Parallel Algorithms For Minimum Spanning Trees

In graph theory a minimum spanning tree (MST) $T$ of a graph $G = (V, E)$ with $, V, = n$ and $, E, = m$ is a tree subgraph of $G$ that contains all of its vertices and is of minimum weight.

MSTs are useful and versatile tools utilised in a wide variety of practical and theoretical fields. For example, a company looking to supply multiple stores with a certain product from a single warehouse might use an MST originating at the warehouse to calculate the shortest paths to each company store. In this case the stores and the warehouse are represented as vertices and the road connections between them - as edges. Each edge is labelled with the length of the corresponding road connection.

If $G$ is edge-unweighted every spanning tree possesses the same number of edges and thus the same weight. In the edge-weighted case, the spanning tree, the sum of the weights of the edges of which is lowest among all spanning trees of $G$, is called a minimum spanning tree (MST). It is not necessarily unique. More generally, graphs that are not necessarily connected have minimum spanning forests, which consist of a union of MSTs for each connected component.

As finding MSTs is a widespread problem in graph theory, there exist many sequential algorithms for solving it. Among them are Prim's, Kruskal's and Borůvka's algorithms, each utilising different properties of MSTs. They all operate in a similar fashion - a subset of $E$ is iteratively grown until a valid MST has been discovered. However, as practical problems are often quite large (road networks sometimes have billions of edges), performance is a key factor. One option of improving it is by parallelising known MST algorithms.

Prim's algorithm

This algorithm utilises the cut-property of MSTs. A simple high-level pseudocode implementation is provided below:

$T \gets \emptyset$
$S \gets \$ where $s$ is a random vertex in $V$
repeat $, V, - 1$ times
find lightest edge $(u,v)$ s.t. $u \in S$ but $v \in (V \setminus S)$
$S \gets S \cup \$
$T \gets T \cup \$
return T

Each edge is observed exactly twice - namely when examining each of its endpoints. Each vertex is examined exactly once for a total of $O(n + m)$ operations aside from the selection of the lightest edge at each loop iteration. This selection is often performed using a priority queue (PQ). For each edge at most one decreaseKey operation ( amortised in $O(1)$) is performed and each loop iteration performs one deleteMin operation ($O(\log n)$). Thus using Fibonacci heaps the total runtime of Prim's algorithm is asymptotically in $O(m + n \log n)$.

It is important to note that the loop is inherently sequential and can not be properly parallelised. This is the case, since the lightest edge with one endpoint in $S$ and on in $V \setminus S$ might change with the addition of edges to $T$. Thus no two selections of a lightest edge can be performed at the same time. However, there do exist some attempts at parallelisation.

One possible idea is to use $O(n)$ processors to support PQ access in $O(1)$ on an EREW-PRAM machine, thus lowering the total runtime to $O(n + m)$.

Kruskal's algorithm

Kruskal's MST algorithm utilises the cycle property of MSTs. A high-level pseudocode representation is provided below.

$T \gets$ forest with every vertex in its own subtree
foreach $(u, v) \in E$ in ascending order of weight
if $u$ and $v$ in different subtrees of $T$
$T \gets T \cup \$
return T

The subtrees of $T$ are stored in union-find data structures, which is why checking whether or not two vertices are in the same subtree is possible in amortised $O(\alpha(m, n))$ where $\alpha(m, n)$ is the inverse Ackermann function. Thus the total runtime of the algorithm is in $O(sort(n) + \alpha(n))$. Here $\alpha(n)$ denotes the single-valued inverse Ackermann function, for which any realistic input yields an integer less than five.

Approach 1: Parallelising the sorting step

Similarly to Prim's algorithm there are components in Kruskal's approach that can not be parallelised in its classical variant. For example, determining whether or not two vertices are in the same subtree is difficult to parallelise, as two union operations might attempt to join the same subtrees at the same time. Really the only opportunity for parallelisation lies in the sorting step. As sorting is linear in the optimal case on $O(\log n)$ processors, the total runtime can be reduced to $O(m \alpha(n))$.

Approach 2: Filter-Kruskal

Another approach would be to modify the original algorithm by growing $T$ more aggressively. This idea was presented by Osipov et al. The basic idea behind Filter-Kruskal is to partition the edges in a similar way to quicksort and filter out edges that connect vertices that belong to the same tree in order to reduce the cost of sorting. A high-level pseudocode representation is provided below.

filterKruskal($G$):
if $m <$ KruskalThreshold:
return kruskal($G$)
pivot = chooseRandom($E$)
$(E_$, $E_) \gets$partition($E$, pivot)
$A \gets$ filterKruskal($E_$)
$E_ \gets$ filter($E_$)
$A \gets A$ $\cup$ filterKruskal($E_$)
return $A$

partition($E$, pivot):
$E_ \gets \emptyset$
$E_ \gets \emptyset$
foreach $(u, v) \in E$:
if weight($u, v$) $\leq$ pivot:
$E_ \gets E_ \cup$
else
$E_ \gets E_ \cup$
return ($E_$, $E_$)

filter($E$):
$E_ \gets \emptyset$
foreach $(u, v) \in E$:
if find-set(u) $\neq$ find-set(v):
$E_ \gets E_ \cup$
return $E_$

Filter-Kruskal is better suited for parallelisation, since sorting, partitioning and filtering have intuitively easy parallelisations where the edges are simply divided between the cores.

Borůvka's algorithm

The main idea behind Borůvka's algorithm is edge contraction. An edge $\$ is contracted by first removing $v$ from the graph and then redirecting every edge $\ \in E$ to $\$. These new edges retain their old edge weights. If the goal is not just to determine the weight of an MST but also which edges it comprises, it must be noted between which pairs of vertices an edge was contracted. A high-level pseudocode representation is presented below.

$T \gets \emptyset$
while $, V, > 0$
$S \gets \emptyset$
for $v \in V$
$S \gets S$ $\cup$ lightest $\ \in E$
for $\ \in S$
contract $\$
$T \gets T \cup S$
return T

It is possible that contractions lead to multiple edges between a pair of vertices. The intuitive way of choosing the lightest of them is not possible in $O(m)$. However, if all contractions that share a vertex are performed in parallel this is doable. The recursion stops when there is only a single vertex remaining, which means the algorithm needs at most $\log n$ iterations, leading to a total runtime in $O(m \log n)$.

Parallelisation

One possible parallelisation of this algorithm yields a polylogarithmic time complexity, i.e. $T(m, n, p) \cdot p \in O(m \log n)$ and there exists a constant $c$ so that $T(m, n, p) \in O(\log^c m)$. Here $T(m, n, p)$ denotes the runtime for a graph with $m$ edges, $n$ vertices on a machine with $p$ processors. The basic idea is the following:

while $, V, > 1$
find lightest incident edges // $O(\frac + \log n + \log p)$
assign the corresponding subgraph to each vertex // $O(\frac + \log n)$
contract each subgraph // $O(\frac + \log n)$

The MST then consists of all the found lightest edges.

This parallelisation utilises the adjacency array graph representation for $G = (V, E)$. This consists of three arrays - $\Gamma$ of length $n + 1$ for the vertices, $\gamma$ of length $m$ for the endpoints of each of the $m$ edges and $c$ of length $m$ for the edges' weights. Now for vertex $i$ the other end of each edge incident to $i$ can be found in the entries between \gamma Gamma [i-1 and $\gamma [\Gamma[i">-1.html" ;"title="Gamma [i-1">Gamma [i-1$ and $\gamma [\Gamma[i$. The weight of the $i$-th edge in $\Gamma$ can be found in $c[i]$. Then the $i$-th edge in $\gamma$ is between vertices $u$ and $v$ if and only if $\Gamma[u] \leq i < \Gamma[u + 1]$ and $\gamma[i] = v$.

Finding the lightest incident edge

First the edges are distributed between each of the $p$ processors. The $i$-th processor receives the edges stored between $\gamma$frac/math> and $\gamma$frac - 1/math>. Furthermore, each processor needs to know to which vertex these edges belong (since $\gamma$ only stores one of the edge's endpoints) and stores this in the array $pred$. Obtaining this information is possible in $O(\log n)$ using $p$ binary searches or in $O(\frac + p)$ using a linear search. In practice the latter approach is sometimes quicker, even though it is asymptotically worse.

Now each processor determines the lightest edge incident to each of its vertices.

$v \gets$ find($\frac$, $\Gamma$)
for $e \gets \frac; e < \frac - 1; e++$
if \Gamma +1= e
$v++$
ifc < c red[v
$pred[v">.html" ;"title="red[v">red[v$
$pred[v\gets e$

Here the issue arises some vertices are handled by more than one processor. A possible solution to this is that every processor has its own $prev$ array which is later combined with those of the others using a reduction. Each processor has at most two vertices that are also handled by other processors and each reduction is in $O(\log p)$. Thus the total runtime of this step is in $O(\frac + \log n + \log p)$.

Assigning subgraphs to vertices

Observe the graph that consists solely of edges collected in the previous step. These edges are directed away from the vertex to which they are the lightest incident edge. The resulting graph decomposes into multiple weakly connected components. The goal of this step is to assign to each vertex the component of which it is a part. Note that every vertex has exactly one outgoing edge and therefore each component is a pseudotree - a tree with a single extra edge that runs in parallel to the lightest edge in the component but in the opposite direction. The following code mutates this extra edge into a loop:

parallel forAll $v \in V$
$w \gets pred[v]$
if $pred[w] = v \land v < w$
pred \gets v

Now every Glossary_of_graph_theory_terms#weakly_connected, weakly connected component is a directed tree where the root has a loop. This root is chosen as the representative of each component. The following code uses doubling to assign each vertex its representative:

while \exists v \in V: pred \neq pred red[v
forAll $v \in V$
pred \gets pred red[v

Now every subgraph is a Glossary_of_graph_theory_terms#star">star