On Thu, 17 Jul 2008, Sam Stickland wrote:
Something that could provide a similar, automated analysis of a TCP stream
capture is what I'm after, although I doubt a standard packet capture will be
able to provided as many metric as web100 stack can.
There are several similar tools designed for I
: Re: Analysing traces for performance bottlenecks
Matt Cable wrote:
> Kevin Oberman 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, bu
Matt Cable wrote:
Kevin Oberman 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 al
Kevin Oberman 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 tcptr
Wireshark can show the throughput on a bits/sec or pps, by IP, etc. This is
under IO Graphs. You'll want to change the time display format of the main
decode window to Seconds Since Beginning of Capture to sync up time with the
graph.
At least that way, you can just focus on the dips in through
> Date: Tue, 15 Jul 2008 11:05:34 +0100
> From: Sam Stickland <[EMAIL PROTECTED]>
>
> 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, windo
A bit more googling has found the Web100 projects NDT
(http://e2epi.internet2.edu/ndt/). I'm currently making a Linux VM that
can run it. It's useful, but I'm still really after something that can
do it's type of analysis from a packet capture.
Sam
Sam Stickland wrote:
Hi,
Are there any pac
One potentially useful piece of software that is a work in progress is
called Pcapdiff. (http://www.eff.org/testyourisp/pcapdiff/)
Written by Seth Schoen and Steven Lucy it's a pretty useful piece of
software. While still in a relative infant stage I think it could mature
into a very useful tool t
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
f
9 matches
Mail list logo
