Re: Analysing traces for performance bottlenecks

Kevin Oberman <oberman <at> es.net> writes:

tcptrace is old and pretty basic, but it can provide a LOT if information. Combined with xplot, the graphs often point to the exact nature of a TCP problem, but you need a really good understanding of TCP to figure anything out.

Wireshark also provides tcptrace-like graphs ("Statistics -> TCP Stream Graph -> Time Sequence Graph (tcptrace)"). They're not quite as pretty, but are just as effective at tracking down all sorts of TCP problems, provided, as Kevin said, you have a really good understanding of how TCP behaves.