# 随机算法 (Fall 2011)/Routing in a Parallel Network

The problem raises from parallel computing. Consider that we have processors, connected by a communication network. The processors communicate with each other by sending and receiving **packets** through the network. We consider the following packet routing problem:

- Every processor is sending a packet to a unique destination. Therefore for the set of processors, the destinations are given by a
**permutation**of , such that for every processor , the processor is sending a packet to processor . - The communication is
**synchronized**, such that for each**round**, every link (an edge of the graph) can forward at most one packet.

With a complete graph as the network. For any permutation of , all packets can be routed to their destinations in parallel with one round of communication. However, such an ideal connectivity is usually not available in reality, either because they are too expensive, or because they are physically impossible. We are interested in the case the graph is **sparse**, such that the number of edges is significantly smaller than the complete graph, yet the distance between any pair of vertices is small, so that the packets can be efficiently routed between pairs of vertices.

## Contents

# Routing on a hypercube

A hypercube (sometimes called Boolean cube, Hamming cube, or just cube) is defined over nodes, for a power of 2. We assume that . A hypercube of dimensions, or a -cube, is an undirected graph with the vertex set , such that for any , and are adjacent if and only if , where is the Hamming distance between and .

A -cube is a -degree regular graph over vertices. For any pair of vertices, the distance between and is at most . (How do we know this? Since it takes at most steps to fix any binary string of length bit-by-bit to any other.) This directly gives us the following very natural routing algorithm.

**Bit-Fixing Routing Algorithm**For each packet:

- Let be the origin and destination of the packet respectively.
- For to , do:

- if then traverse the edge .

- Oblivious routing algorithms
- This algorithm is blessed with a desirable property: at each routing step, the choice of link depends only on the the current node and the destination. We call the algorithms with this property
**oblivious**routing algorithms. (Actually, the standard definition of obliviousness allows the choice also depends on the origin. The bit-fixing algorithm is even more oblivious than this standard definition.) Compared to the routing algorithms which are adaptive to the path that the packet traversed, oblivious routing is more simple thus can be implemented by smaller routing table (or simple devices called**switches**).

- Queuing policies
- When routing packets in parallel, it is possible that more than one packets want to use the same edge at the same time. We assume that a queue is associated to each edge, such that the packets to be delivered through an edge are put into the queue associated with the edge. With some
**queuing policy**(e.g. FIFO, or furthest to do), the queued packets are delivered through the edge by at most one packet per each round.

For the bit-fixing routing algorithm defined above, regardless of the queuing policy, there always exists a bad permutation which specifies the destinations, such that it takes steps by the bit-fixing algorithm to route all packets to their destinations. (You can prove this by yourself.)

This is pretty bad, because we expect that the routing time is comparable to the diameter of the network, which is only for hypercube.

The lower bound actually applies generally for any deterministic oblivious routing algorithms:

**Theorem [Kaklamanis, Krizanc, Tsantilas, 1991]**- In any -node communication network with maximum degree , any deterministic oblivious algorithm for routing an arbitrary permutation requires parallel communication steps in the worst case.

The proof of the lower bound is rather technical and complicated. However, the intuition is quite clear: for any oblivious rule for routing, there always exists a permutation which causes a very high **congestion**, such that many packets have to be delivered through the same edge, thus no matter what queuing policy is used, the maximum delay must be very high.

# Average-case Analysis for Independent Destinations

We analyze the average-case performance of the bit-fixing routing algorithm. We relax the problem to non-permutation destinations. That is, instead of restricting that every processor has a distinct destination, we now allow each processor choose an arbitrary destination in .

For the average case, for each node , its destination is a uniformly and independently random node from .

For each node , let denote the route for to its random destination . is a sequence of edges along the bit-fixing route from to .

## Reduce the delay of a route to the number of packets that pass through the route

We consider the **delay** incurred by each node, which is the total time that its packet is waiting in the queue. The total running time of the algorithm is bounded by the maximum delay plus .

We assume that the queueing policy satisfies a very natural requirement:

- Natural queuing assumption
- If a queue is not empty at the beginning of a time step, some packet is sent along the edge associated with that queue during that time step.

**Lemma 2.1**- With the above assumption of the queuing policy, the delay inccured by is at most the number of packets whose routes pass through at least one edge in .

**Proof.**See Lemma 4.5 in the textbook [MR].

## Represent the delay as the sum of independent trials

Let the random variable indicate whether and share at least one edge. That is,

Fix a node and the corresponding route . The random variable gives the total number of packets whose routes pass through . Due to Lemma 2.1, gives an upper bound on the delay inccured by .

We will then bound . Note that for , are independent trials (because the destinations of and are independent), thus we can apply the Chernoff bound. To do so, we must estimate the expectation .

## Estimate the expectation of the sum

For any edge in the hypercube, let the random variable denote the number of routes that pass through . As we argued above that is the number of packets that pass though the route , then obviously

where we abuse the notation to denote the edge appeared in the route .

Therefore,

For every node , the length of the route , denoted , is the number of different bits between and the last node in the route (because of the "bit-fixing"). For the uniformly random destination, (a random node in expectedly flips bits in any fixed ). Thus,

It is obvious that we can count the sum of lengths of a set of routes by accumulating their passes through edges, that is

Therefore,

where the sum is taken over all edges in the hypercube.

An important observation is that the distribution of 's are all symmetric, thus all 's are equal. The number of edges in the hypercube is . Therefore, for every edge in the hupercube,

The length of is at most . Due to , the expectation of is .

## Apply the Chernoff bound

We apply the following form of the Chernoff bound:

**Chernoff bound**- Let , where are independent Poisson trials. Let . Then for ,

- Let , where are independent Poisson trials. Let . Then for ,

It holds that . By applying the Chernoff bound,

- .

Note that only gives the bound on the delay incurred by a particular node . By the union bound,

The running time is the maximum delay plus the length of a route, thus is with probability .

# A two-phase randomized routing algorithm

The above analysis of the performance of bit-fixing for independent random destinations hints us that we can first route the packets to random "relay"s to avoid the high congestion. This was first discovered by Leslie Valiant who uses the idea to give a simple and elegant randomized routing algorithm for permutation routing.

The algorithm works in two phases.

**Two-Phase Routing Algorithm**For each packet:

**Phase I:**Route the packet to a random destination using the bit-fixing algorithm.**Phase II:**Route the packet from the random location to its final destination using the bit-fixing algorithm.

It looks counter-intuitive that first routing the packets to irrelevant intermediate nodes actually improves the overall performance.

To simplify the analysis, we assume that no packet is sent in Phase II before all packets have finished Phase I.

Phase I is exactly the bit-fixing routing for uniformly and independently random destinations, which as we analyzed in the last section, has a running time within for probability at least .

The Phase II is a "backward" running of Phase I. All the analysis of Phase I can be directly applied to Phase II. Thus, the running time of Phase II is with probability . By the union bound, the total running time of the randomized routing algorithm is no more than with high probability.