From: Jesper Dangaard Brouer <jbrouer@redhat.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "codel@lists.bufferbloat.net" <codel@lists.bufferbloat.net>,
"bloat@lists.bufferbloat.net" <bloat@lists.bufferbloat.net>
Subject: Re: [Codel] [Bloat] Network test tools for many parallel/concurrent connections?
Date: Tue, 14 May 2013 21:20:27 +0200 [thread overview]
Message-ID: <20130514212027.007f6060@redhat.com> (raw)
In-Reply-To: <20130514084726.0fcd715a@nehalam.linuxnetplumber.net>
On Tue, 14 May 2013 08:47:26 -0700
Stephen Hemminger <stephen@networkplumber.org> wrote:
> 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.
Well perhaps it would be easier to use some apache load test tool, but
in this test scenario I just want see how well fq_codel scales with
many concurrent bulk transfers.
Can people on the list recommend any commercial test-equip solutions?
--
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
prev parent reply other threads:[~2013-05-14 19:20 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
2013-05-14 18:13 ` Jim Gettys
2013-05-14 19:20 ` Jesper Dangaard Brouer [this message]
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=20130514212027.007f6060@redhat.com \
--to=jbrouer@redhat.com \
--cc=bloat@lists.bufferbloat.net \
--cc=codel@lists.bufferbloat.net \
--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