General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: Aaron Wood <woody77@gmail.com>, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] different speeds on different ports? (benchmarking fun)
Date: Thu, 21 Sep 2017 14:51:02 +0200	[thread overview]
Message-ID: <7D7658AA-DFC7-40D1-9D1D-C17D50E706EB@gmx.de> (raw)
In-Reply-To: <87o9q41ev3.fsf@toke.dk>

Hi Toke, Stefan, Aaron,


> On Sep 21, 2017, at 13:16, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
> 
>> It would be interesting if we could run some netperf tests using port
>> 80/443 for the listening socket for the data connection (although if
>> doing deep-packet inspection, we might need to use an actual HTTP
>> transfer).
> 
> Trouble with this is that netserver would have to run as root to be able
> to bind to the ports; it does that dynamically, so binding at startup
> and dropping privileges won't work. Also it would mean that no other
> services could run on those ports.
> 
> For your use case, my guess would also be differences in the server
> connection (or peering), though. I do believe dslreports will open
> connections to multiple servers; you could try running one of the
> rtt_fair Flent tests against multiple servers to see if you can push
> more data that way...

	After a free registration you can actually select the servers you want to test against as well as the number of concurrent streams. There even is a command line version of the dslreports speedtest (https://www.dslreports.com/forum/speedtestbinary) which offers the following options:
bash-3.2$ ./dslrcli-darwin-amd64 --help
NAME:
   Dslrcli - Test network speed

USAGE:
   dslrcli-darwin-amd64 [global options] command [command options] [arguments...]
   
VERSION:
   0.1 - 13-Dec-2016
   
AUTHOR(S):
   DSLReports.com <www.dslreports.com> 
   
COMMANDS:
     daemonmode, W  run in daemonmode
     help, h        Shows a list of commands or help for one command

GLOBAL OPTIONS:
   --debug, -d                
   --printlog, -l             Prints the log on the screen.
   --uname value              Your DslReports.com username - OPTIONAL.
   --upassword value          Your DslReports.com password - OPTIONAL.
   --machinename value        A machine name for the daemon mode. (default: "machine1")
   --apikey value             Your DslReports.com API Key - OPTIONAL.
   --up value                 Number of streams to use for upload tests (default: "4")
   --uploadtime value         Time limit to end the upload test in. (default: "15")
   --down value               Number of streams to use for download tests. (default: "6")
   --hz value                 The frequency (in hz) at which speed samples are to be taken. (default: 1)
   --downloadtime value       Time limit to end the download test in. (default: "15")
   --perserver value          The number of streams per server. (default: "3")
   --totalstreams value       The total number of streams to use for the speedtests - OPTIONAL (default: "X")
   --comment value, -c value  Include comment with test result.
   --output value, -o value   Specify type of output . 'json' and 'csv' are currently supported. (default: "default")
   --upload-only              Performs the Upload test only.
   --download-only            Performs the Download test only.
   --daemon                   Runs the DslReports client in daemon mode.
   --daemon-cmd value         Daemon sub command install, uninstall.
   --authfile value           A json file containing username and password for authentication.
   --platform value           Specify a platform (GPRS, 3G, 4G, WiFi, Wireless, Satellite, DSL, Cable, Fiber, Unsure). (default: "Unsure")
   --latlong value            Specify a latitude longitude of the region to select servers from. In the form -latlong a,b
   --ipv4                     IPv4
   --ipv6                     IPv6
   --help, -h                 show help
   --version, -v              print the version
   
So you can specify the number of servers (--totalstreams MM; totalstreams/perserver shoukld equal number of servers) as well as the number of flows per server (--perserver NN). Anyway, no back to the regularly scheduled programming...

Best Regards
	Sebastian


> 
> -Toke
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat


  reply	other threads:[~2017-09-21 12:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-30  5:15 Aaron Wood
2017-09-21  2:06 ` Dave Taht
2017-09-21  2:34 ` Dave Taht
2017-09-21 10:58 ` Stefan Alfredsson
2017-09-21 11:16 ` Toke Høiland-Jørgensen
2017-09-21 12:51   ` Sebastian Moeller [this message]
2017-09-22  0:26   ` David Lang
2017-09-21 14:50 ` Colin Dearborn
2017-09-21 15:13   ` Aaron Wood
2017-09-21 15:16     ` Aaron Wood
2017-09-23  2:51       ` Aaron Wood

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=7D7658AA-DFC7-40D1-9D1D-C17D50E706EB@gmx.de \
    --to=moeller0@gmx.de \
    --cc=bloat@lists.bufferbloat.net \
    --cc=toke@toke.dk \
    --cc=woody77@gmail.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