From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ia0-x229.google.com (mail-ia0-x229.google.com [IPv6:2607:f8b0:4001:c02::229]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id CD9CE21F151; Tue, 14 May 2013 10:07:33 -0700 (PDT) Received: by mail-ia0-f169.google.com with SMTP id k38so946291iah.28 for ; Tue, 14 May 2013 10:07:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=ZZKhra8FKyNWwq5x45Z0nYy7hVoXjld/0OczI/HiQbs=; b=fCTyCvo3eHL7Fqxb8IW44VOWmJUWi/ZRMDA6EOcugWRy77lx1EptDIGamCqYDe4HRF Ro+r4EUxjnqzPW07C1XkiKO/4iAjck0L4ujwvnRuY4tnjgYdiWd++kmFFJqQfI79I43b LY2uKRZFjDqp2NQMseIy0kJYsa4AigSuC9N+lq8O09jtFYrGzKv4BjJQLPgZZhF2k9za wsRU76p3wYi+jEqc993oS5EyLgJwDG2fEELoqjMowqeLmZdVUqDrO+MupgkkjntqaWCy ZS7EkNaO1X7yM/VptwkO8EnInK3HCQ0/6ExFYwSsNGvjIJnI/qRIuMvZDkd4FNTRG8Rz YOcQ== MIME-Version: 1.0 X-Received: by 10.50.120.4 with SMTP id ky4mr2620224igb.86.1368550918922; Tue, 14 May 2013 10:01:58 -0700 (PDT) Received: by 10.64.9.114 with HTTP; Tue, 14 May 2013 10:01:58 -0700 (PDT) Received: by 10.64.9.114 with HTTP; Tue, 14 May 2013 10:01:58 -0700 (PDT) In-Reply-To: <20130514084726.0fcd715a@nehalam.linuxnetplumber.net> References: <20130514154838.2d9622b7@redhat.com> <20130514084726.0fcd715a@nehalam.linuxnetplumber.net> Date: Tue, 14 May 2013 10:01:58 -0700 Message-ID: From: Dave Taht To: Stephen Hemminger Content-Type: multipart/alternative; boundary=047d7b8746d4612bed04dcb09735 Cc: "codel@lists.bufferbloat.net" , Jesper Dangaard Brouer , bloat Subject: Re: [Codel] [Bloat] Network test tools for many parallel/concurrent connections? X-BeenThere: codel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: CoDel AQM discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 May 2013 17:07:34 -0000 --047d7b8746d4612bed04dcb09735 Content-Type: text/plain; charset=ISO-8859-1 On May 14, 2013 12:21 PM, "Stephen Hemminger" wrote: > > On Tue, 14 May 2013 15:48:38 +0200 > Jesper Dangaard Brouer 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 --047d7b8746d4612bed04dcb09735 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable


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 <jbrou= er@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" analys= e one of the TCP
> > streams to see how the congestion window, outstanding-win/data is=
> > behaving. =A0Back in 2005 I used-to-use a tool =A0called
> > "tcptrace" (http://= www.tcptrace.org).
> > Have any better tools surfaced?
> >
>
>
> You may want to look at some of the "realistic" load tools s= ince
> 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 r= eal 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 b= andwidth.

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 almo= st never shows a 5 minute average over 60% of capacity, but I know full wel= l that Netflix users are clobbering things on a 10 sec interval and that th= ere 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

--047d7b8746d4612bed04dcb09735--