[105981] in North American Network Operators' Group
Re: Analysing traces for performance bottlenecks
daemon@ATHENA.MIT.EDU (Kevin Oberman)
Tue Jul 15 15:04:13 2008
To: Sam Stickland <sam_mailinglists@spacething.org>
In-Reply-To: Your message of "Tue, 15 Jul 2008 11:05:34 BST."
<487C766E.9070501@spacething.org>
Date: Tue, 15 Jul 2008 12:03:25 -0700
From: "Kevin Oberman" <oberman@es.net>
Cc: NANOG list <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
--==_Exmh_1216148605_36079P
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
> Date: Tue, 15 Jul 2008 11:05:34 +0100
> From: Sam Stickland <sam_mailinglists@spacething.org>
>
> Hi,
>
> Are there any packages (or Wireshark options that I've missed) that can
> follow a TCP stream and determine the limiting factor on throughput. E.g
> Latency, packet loss, out of sequence packets, window size, or even just
> the senders rate onto the wire. I know how to analyse a trace by hand
> for performance issues, but it's relatively time consuming.
>
> Googling for variations on "Analyse TCP stream limit throughput" didn't
> find anything.
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.
--
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman@es.net Phone: +1 510 486-8634
Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751
--==_Exmh_1216148605_36079P
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (FreeBSD)
Comment: Exmh version 2.5 06/03/2002
iD8DBQFIfPR9kn3rs5h7N1ERAq7xAJ4gXt5Gabgibu70FnJJviKp3xGJPwCfey4H
5KnCHeReqhUXf44LC9/Myuw=
=Ziul
-----END PGP SIGNATURE-----
--==_Exmh_1216148605_36079P--
