From: Dave Taht <dave.taht@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "codel@lists.bufferbloat.net" <codel@lists.bufferbloat.net>,
Jesper Dangaard Brouer <jbrouer@redhat.com>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Codel] [Bloat] Network test tools for many parallel/concurrent connections?
Date: Tue, 14 May 2013 10:01:58 -0700 [thread overview]
Message-ID: <CAA93jw4WqkWHrGpJ_c+O+W9cgcWnJObfyJs-0M3Ovzw4nHpXQA@mail.gmail.com> (raw)
In-Reply-To: <20130514084726.0fcd715a@nehalam.linuxnetplumber.net>
[-- Attachment #1: Type: text/plain, Size: 1996 bytes --]
On May 14, 2013 12:21 PM, "Stephen Hemminger" <stephen@networkplumber.org>
wrote:
>
> On Tue, 14 May 2013 15:48:38 +0200
> Jesper Dangaard Brouer <jbrouer@redhat.com> wrote:
>
> >
> > (I'm testing fq_codel and codel)
> >
> > I need a test tool that can start many TCP streams (>1024).
> > During/after the testrun I want to know if the connections got a fair
> > share of the bandwidth.
> >
> > Can anyone recomment tools for this?
> >
> > After the test I would also like to, "deep-dive" analyse one of the TCP
> > streams to see how the congestion window, outstanding-win/data is
> > behaving. Back in 2005 I used-to-use a tool called
> > "tcptrace" (http://www.tcptrace.org).
> > Have any better tools surfaced?
> >
>
>
> You may want to look at some of the "realistic" load tools since
> in real life not all flows are 100% of bandwidth and long lived.
You may want to look at some realistic load tools since in real life
99.9Xx% of all flows are 100% of bandwidth AND long lived.
At various small timescales a flow or flows can be 100% of bandwidth.
But it still takes one full rate flow to mess up your whole day.
This is why I suggested ab.
Here bandwidth is an average usually taken over a second and often much
more. If you sample at a higher resolution, like a ms, you are either at
capacity or empty.
Another way of thinking about it is for example, mrtg takes samples every
30 seconds and the most detailed presentation of that data it gives you is
on a 5 minute interval. The biggest fq codel site I have almost never shows
a 5 minute average over 60% of capacity, but I know full well that Netflix
users are clobbering things on a 10 sec interval and that there are
frequent peaks where it is running at capacity for a few seconds at a time
from looking at the data on a much finer interval and the fq codel drop
statistics.
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
[-- Attachment #2: Type: text/html, Size: 2698 bytes --]
next prev parent reply other threads:[~2013-05-14 17:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-14 13:48 [Codel] " Jesper Dangaard Brouer
2013-05-14 14:46 ` [Codel] [Bloat] " Dave Taht
2013-05-14 19:48 ` Jesper Dangaard Brouer
2013-05-14 22:26 ` Rick Jones
2013-05-14 15:47 ` Stephen Hemminger
2013-05-14 17:01 ` Dave Taht [this message]
2013-05-14 18:13 ` Jim Gettys
2013-05-14 19:20 ` Jesper Dangaard Brouer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/codel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw4WqkWHrGpJ_c+O+W9cgcWnJObfyJs-0M3Ovzw4nHpXQA@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=codel@lists.bufferbloat.net \
--cc=jbrouer@redhat.com \
--cc=stephen@networkplumber.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox