Why should avoid TIME_WAIT state at Busy Servers

In Myrinet, hosts becomes the performance bottleneck in many cases. Currently, heavily loaded servers potentially keep thousands of connections in TIME-WAIT state, which consume memory and can slow active connections.

      server                            client
      -----------------------------------------------------------
      ESTABLISHED                       ESTABLISHED
      (get application close)
      goto FIN_WAIT_1
      send FIN           ---FIN--->
                                        goto CLOSE_WAIT
                        <---ACK---      send ACK
      goto FIN_WAIT_2
                                        (get application close)
                                        goto LAST_ACK
                        <---FIN---      send FIN
      goto TIME_WAIT
      send ACK           ---ACK--->
                                        goto CLOSED

Lots of PCBs for the connections at TIME_WAIT state limits the higher utilization of high speed network. Our goal is to try avoid TIME_WAIT state at busy servers and release the burdern of the busy servers to make higher utilization of high-speed network. We have two solutions in different ways.

Go back to the ATOMIC-2 home page. / Go back to the ISI home page. ISI Logo

This page is written and maintained by the ATOMIC-2 group.
Please mail us any problems with or comments about this page.
Last modified July 11, 1997.