MIT researchers develop new network-management system to cut down on data traffic jams


Credit: Thinkstock

MIT researchers have created a new network-management system, called Fastpass, that they say cuts down on the long wait times that occur during periods of heavy network congestion. The research team will present its findings during the ACM Special Interest Group on Data Communication conference in mid August.

In a data center, every time a person makes a request, multiple packets of data have to get passed around via a router from one end to the other. When a lot of people are making requests, these data packets can end up getting clogged in the router as the router sets aside the data packets it can’t handle in a queue.

Diagram showing reduced latency

Diagram showing reduced latency

At the heart of the appropriately named Fastpass system is a centralized server called an arbiter. The MIT researchers claim that each time a router or some other network node like a switch or a bridge wants to shoot out data based on a user request, it first passes the request over to the arbiter, which acts as a sort of overseer of all network nodes and requests. Based on the arbiter’s knowledge of the networking system as well as handy timeslot allocation and path assignment algorithms, it can determine the best networking route and time to send the request through in order to prevent a data packet pileup.

An excerpt from the MIT research paper describes the technical aspects of the Fastpass system:

The MIT team apparently tested out Fastpass in a Facebook (S FB) data center and found that the average queue length of the routers was cut down by 99.6 percent. Even during periods of heavy network traffic, the time it took for a request to be sent and retrieved was reduced from 3.56 microseconds to 0.23 microseconds.


Jonathan Vanian

According to the MIT paper, it seems like if an arbiter gets booted for some reason, another arbiter gets called in to take over. From the paper: “Conservative timing can ensure that by the time an arbiter failure is detected and the secondary takes over, no allocations made by the failed arbiter remain in the network.”

Comments are closed.