From: Rich Brown <richb.hanover@gmail.com>
To: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] netperf server configuration
Date: Tue, 27 Sep 2016 12:09:51 -0400 [thread overview]
Message-ID: <D0D9E470-E852-4F49-B987-E5501C74E499@gmail.com> (raw)
> Dave Täht recently wrote:
>
> I just put a netperf server up in linode's freemont, ca, cloud (kvm
> paravirtualized hardware), with sch_fq enabled, ecn disabled, and bbr
> as the default cc. (reno and cubic are also allowed)
That raises the question about the "proper" configuration for a netperf server.
I run the server at netperf.bufferbloat.net. It's a plain-vanilla OpenVZ VPS on a (Ramnode.com) server in Atlanta, running Ubuntu 15.10 server. Network config as-is, out of the box - I haven't done any tweaking.
Are there changes I might/should make? Thanks.
Rich
reply other threads:[~2016-09-27 16:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D0D9E470-E852-4F49-B987-E5501C74E499@gmail.com \
--to=richb.hanover@gmail.com \
--cc=cerowrt-devel@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