[105983] in North American Network Operators' Group
Re: Analysing traces for performance bottlenecks
daemon@ATHENA.MIT.EDU (Matt Cable)
Tue Jul 15 18:08:34 2008
To: nanog@nanog.org
From: Matt Cable <wozz@wookie.net>
Date: Tue, 15 Jul 2008 22:08:08 +0000 (UTC)
X-Complaints-To: usenet@ger.gmane.org
Errors-To: nanog-bounces@nanog.org
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.
