General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Isaac Konikoff <konikofi@candelatech.com>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Network test tools for many parallel/concurrent connections?
Date: Tue, 14 May 2013 09:28:54 -0700	[thread overview]
Message-ID: <51926646.3010505@candelatech.com> (raw)
In-Reply-To: <CAA93jw54i8Y1Sc18GiNjUBxt_Kw1_FdW6TrK4+Xu3Q8A6JOaYA@mail.gmail.com>

Candela makes a Linux based network traffic test tool called 
LANforge-FIRE. It can generate in excess of 50,000 TCP connections among 
other features. It is a proprietary tool, but we'll send out free 
licenses to students and those working on non-commercial open source 
projects.

Thanks,
Isaac



On 05/14/2013 07:46 AM, Dave Taht wrote:
> I still use tcptrace and xplot.org <http://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
> <mailto: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 <mailto:Bloat@lists.bufferbloat.net>
>     https://lists.bufferbloat.net/listinfo/bloat
>
>
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>


-- 
Isaac Konikoff
Candela Technologies
konikofi@candelatech.com
Office: +1 360 380 1618
Cell: +1 360 389 2453
Fax: +1 360 380 1431

  reply	other threads:[~2013-05-14 16:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-14 13:48 Jesper Dangaard Brouer
2013-05-14 14:46 ` Dave Taht
2013-05-14 16:28   ` Isaac Konikoff [this message]
2013-05-14 20:09     ` Jesper Dangaard Brouer
2013-05-14 19:48   ` [Bloat] [Codel] " Jesper Dangaard Brouer
2013-05-14 22:26     ` Rick Jones
2013-05-15 10:27       ` Jesper Dangaard Brouer
2013-05-15 16:37         ` Rick Jones
2013-05-14 15:47 ` [Bloat] " 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/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51926646.3010505@candelatech.com \
    --to=konikofi@candelatech.com \
    --cc=bloat@lists.bufferbloat.net \
    /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