From: Dave Taht <dave.taht@gmail.com>
To: Jesper Dangaard Brouer <jbrouer@redhat.com>
Cc: codel@lists.bufferbloat.net, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Codel] [Bloat] Network test tools for many parallel/concurrent connections?
Date: Tue, 14 May 2013 07:46:02 -0700 [thread overview]
Message-ID: <CAA93jw54i8Y1Sc18GiNjUBxt_Kw1_FdW6TrK4+Xu3Q8A6JOaYA@mail.gmail.com> (raw)
In-Reply-To: <20130514154838.2d9622b7@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1250 bytes --]
I still use tcptrace and xplot.org for deep dives.
I just fired off 2048 netperfs to localhost on my laptop. It started
bogging down at 1000 but made it to the end, all connections chugging away.
Probably a better tool would be the apache benchmark `ab` or something else
that is built to stress out web sites.
On May 14, 2013 10:15 AM, "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?
>
> --
> Best regards,
> Jesper Dangaard Brouer
> MSc.CS, Sr. Network Kernel Developer at Red Hat
> Author of http://www.iptv-analyzer.org
> LinkedIn: http://www.linkedin.com/in/brouer
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
[-- Attachment #2: Type: text/html, Size: 1966 bytes --]
next prev parent reply other threads:[~2013-05-14 14:46 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 ` Dave Taht [this message]
2013-05-14 19:48 ` [Codel] [Bloat] " Jesper Dangaard Brouer
2013-05-14 22:26 ` Rick Jones
2013-05-14 15:47 ` Stephen Hemminger
2013-05-14 17:01 ` Dave Taht
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=CAA93jw54i8Y1Sc18GiNjUBxt_Kw1_FdW6TrK4+Xu3Q8A6JOaYA@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=codel@lists.bufferbloat.net \
--cc=jbrouer@redhat.com \
/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