Cluster:LowLatency

From Earlham CS Department
Revision as of 18:56, 1 September 2005 by Skylar (talk | contribs)
Jump to navigation Jump to search

Plan (updated August 28, 2005)

  • Decide on two benchmarks, one micro (low-level) and one application, probably MD with GROMACS in a form that's latency bound on bazaar & Cairo. Set these up on bazaar and Cairo and start tests.
  • Formal literature search and preliminary review.
  • Test tcp_low_latency - does it work? If so, what does it do _exactly_
  • Show that latency is in the network stack, either by reference or by test (preferrably the former since it will take less time).

Notes

  • Comparisons & Instrumentation
  • Low Latency Kernel Option
    • net.ipv4.tcp_low_latency sysctl
      • /proc/sys/net/ipv4/tcp_low_latency
    • From /usr/src/linux/Documentation/networking/ip-sysctl.txt
       tcp_low_latency - BOOLEAN
       If set, the TCP stack makes decisions that prefer lower
       latency as opposed to higher throughput.  By default, this
       option is not set meaning that higher throughput is preferred.
       An example of an application where this default should be
       changed would be a Beowulf compute cluster.
       Default: 0

Ideas

  • Reduce error checking to improve performance
  • Reduce number of memory copies, maybe by not being fully TCP/IP-compliant?
  • Look into STP (scheduled transfer protocol)

Links