nanog mailing list archives
Analysing traces for performance bottlenecks
From: Sam Stickland <sam_mailinglists () spacething org>
Date: Tue, 15 Jul 2008 11:05:34 +0100
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.
Sam
Current thread:
- Analysing traces for performance bottlenecks Sam Stickland (Jul 15)
- Re: Analysing traces for performance bottlenecks Tim Eberhard (Jul 15)
- Re: Analysing traces for performance bottlenecks Sam Stickland (Jul 15)
- Re: Analysing traces for performance bottlenecks Kevin Oberman (Jul 15)
- Re: Analysing traces for performance bottlenecks Matt Cable (Jul 15)
- Re: Analysing traces for performance bottlenecks Sam Stickland (Jul 17)
- RE: Analysing traces for performance bottlenecks Bulger, Tim (Jul 17)
- RE: Analyzing traces for performance bottlenecks Tim Sanderson (Jul 17)
- Re: Analyzing traces for performance bottlenecks Randy Bush (Jul 17)
- Re: Analysing traces for performance bottlenecks Matt Cable (Jul 15)
- Re: Analysing traces for performance bottlenecks Sean Donelan (Jul 17)
- <Possible follow-ups>
- Re: Analysing traces for performance bottlenecks rcheung (Jul 15)