Internet speed test using Terminal - Revision history

Pio2pio: /* iperf */

2019-06-03T11:17:28Z

iperf

← Older revision		Revision as of 13:17, 3 June 2019
Line 106:		Line 106:
	Switches:		Switches:
	<source lang=bash>		<source lang=bash>
	# -t option ~~used in the above command~~ tells to transfer data for X seconds		# -s --server run in server mode, -D run as a daemon in the background
			# -c --client connect to server from client
			# -t time option tells to transfer data for X seconds
			# -p --port server port to listen on/connect to
	# -P --parallel n parallel client streams, iperf3 is single threaded, so if you are CPU bound, this will not yield higher throughput.		# -P --parallel n parallel client streams, iperf3 is single threaded, so if you are CPU bound, this will not yield higher throughput.
	# -p --~~port server port to listen on/connect~~ to		# -l --len length of buffer to read or write (default 8 KB)
	# -w desired window size value		# -w desired window size value
	~~# -l, --len length of buffer to read or write (default 8 KB)~~
	# -u --udp use UDP rather than TCP		# -u --udp use UDP rather than TCP
	# -M, --mss set TCP maximum segment size (MTU - 40 bytes)		# -M --mss set TCP maximum segment size (MTU - 40 bytes)
	# -f m displays results in megabytes		# -f m displays results in megabytes
	~~# -s, --server run in server mode, -D run as a daemon in the background~~
	~~# -c --client connect to server from client~~
	# -r bidirectional test individually, use -d --dualtest to test simultaneously		# -r bidirectional test individually, use -d --dualtest to test simultaneously
	</source>		</source>

Pio2pio: /* iperf */

2019-06-03T11:14:09Z

iperf

← Older revision		Revision as of 13:14, 3 June 2019
Line 50:		Line 50:
	<code>-P</code> splits the test into a number of streams. So, to just measure throughput use <code>-P 1</code>, then increase number of streams to get more realistic data.		<code>-P</code> splits the test into a number of streams. So, to just measure throughput use <code>-P 1</code>, then increase number of streams to get more realistic data.


			{\| class="wikitable"
			\|+ iperf3 of AWS VPN Gw and Azure Virtual Network Gateway. Note -R flag reverse the direction of a test, so that the server sends data to the client.
			\|-
			! Server listening (AWS)
			! Client connecting (Azure)
			\|-
			\| <source lang="bash">
			ec2-user@linux2 10.111.1.11$ iperf3 -s -p 8888
			-----------------------------------------------------------
			Server listening on 8888
			-----------------------------------------------------------
			Accepted connection from 10.222.2.22, port 34510
			[ 8] local 10.111.1.11 port 8888 connected to 10.222.2.22 port 34512
			[ ID] Interval Transfer Bandwidth Retr Cwnd
			[ 8] 0.00-1.00 sec 73.2 MBytes 614 Mbits/sec 279 561 KBytes
			[ 8] 1.00-2.00 sec 69.9 MBytes 587 Mbits/sec 14 450 KBytes
			[ 8] 2.00-3.00 sec 56.5 MBytes 474 Mbits/sec 6 402 KBytes
			[ 8] 3.00-4.00 sec 65.4 MBytes 548 Mbits/sec 0 507 KBytes
			[ 8] 4.00-5.00 sec 70.3 MBytes 589 Mbits/sec 0 596 KBytes
			[ 8] 5.00-6.00 sec 69.9 MBytes 587 Mbits/sec 18 502 KBytes
			[ 8] 6.00-7.00 sec 73.7 MBytes 619 Mbits/sec 0 596 KBytes
			[ 8] 7.00-8.00 sec 63.1 MBytes 529 Mbits/sec 6 509 KBytes
			[ 8] 8.00-9.00 sec 73.4 MBytes 616 Mbits/sec 6 423 KBytes
			[ 8] 9.00-10.00 sec 54.4 MBytes 456 Mbits/sec 4 398 KBytes
			[ 8] 10.00-10.04 sec 2.69 MBytes 536 Mbits/sec 0 402 KBytes
			- - - - - - - - - - - - - - - - - - - - - - - - -
			[ ID] Interval Transfer Bandwidth Retr
			[ 8] 0.00-10.04 sec 672 MBytes 562 Mbits/sec 333 sender
			[ 8] 0.00-10.04 sec 0.00 Bytes 0.00 bits/sec receiver
			</source>
			\| <source lang=bash> ubuntu@bastion-1:~$ iperf3 -c 10.111.1.11 -l 1300 -p 8888 -P 1 -R
			Connecting to host 10.111.1.11, port 8888
			Reverse mode, remote host 10.111.1.11 is sending
			[ 4] local 10.222.2.22 port 34512 connected to 10.111.1.11 port 8888
			[ ID] Interval Transfer Bandwidth
			[ 4] 0.00-1.00 sec 74.1 MBytes 622 Mbits/sec
			[ 4] 1.00-2.00 sec 69.4 MBytes 582 Mbits/sec
			[ 4] 2.00-3.00 sec 55.6 MBytes 467 Mbits/sec
			[ 4] 3.00-4.00 sec 66.4 MBytes 557 Mbits/sec
			[ 4] 4.00-5.00 sec 70.9 MBytes 595 Mbits/sec
			[ 4] 5.00-6.00 sec 69.3 MBytes 581 Mbits/sec
			[ 4] 6.00-7.00 sec 74.2 MBytes 623 Mbits/sec
			[ 4] 7.00-8.00 sec 62.7 MBytes 526 Mbits/sec
			[ 4] 8.00-9.00 sec 73.0 MBytes 613 Mbits/sec
			[ 4] 9.00-10.00 sec 54.1 MBytes 454 Mbits/sec
			- - - - - - - - - - - - - - - - - - - - - - - - -
			[ ID] Interval Transfer Bandwidth Retr
			[ 4] 0.00-10.00 sec 672 MBytes 564 Mbits/sec 333 sender
			[ 4] 0.00-10.00 sec 670 MBytes 562 Mbits/sec receiver
			</source>
			\|}

Pio2pio: /* iperf */

2019-06-03T11:02:59Z

iperf

← Older revision		Revision as of 13:02, 3 June 2019
Line 35:		Line 35:

	= iperf =		= iperf =
	This measures the bandwidth between two locations where one is set as a server and another as a client.		This measures the bandwidth between two locations where one is set as a server and another as a client. Note there is <code>iperf</code> and <code>iperf3</code> that are not compatible.

	Start up server listening on port 8888. By default it is TCP port 5001 and TCP window size 64.0KB		Start up server listening on port 8888. By default it is TCP port 5001 and TCP window size 64.0KB
	/opt/systems/bin/iperf -s -p 8888		<source lang=bash>
			/opt/systems/bin/iperf -s -p 8888
			</source>


	Connect client to server on port 8888		Connect client to server on port 8888
	/opt/systems/bin/iperf -c your.server.com -l 1300 -p 8888 -P 10		<source lang=bash>
			/opt/systems/bin/iperf -c your.server.com -l 1300 -p 8888 -P 10
			</source>

			<code>-P</code> splits the test into a number of streams. So, to just measure throughput use <code>-P 1</code>, then increase number of streams to get more realistic data.



	Switches:		Switches:
	:-t option used in the above command tells to transfer data for X seconds		<source lang=bash>
	:-P ~~divide results into X time frames aka lines printed~~		# -t option used in the above command tells to transfer data for X seconds
	:-p --port server port to listen on/connect to		# -P --parallel n parallel client streams, iperf3 is single threaded, so if you are CPU bound, this will not yield higher throughput.
	:-w desired window size value		# -p --port server port to listen on/connect to
	:-l, --len length of buffer to read or write (default 8 KB)		# -w desired window size value
	:-u --udp use UDP rather than TCP		# -l, --len length of buffer to read or write (default 8 KB)
	:-M, --mss set TCP maximum segment size (MTU - 40 bytes)		# -u --udp use UDP rather than TCP
	:-f m displays results in megabytes		# -M, --mss set TCP maximum segment size (MTU - 40 bytes)
	:-s, --server run in server mode, -D run as a daemon in the background		# -f m displays results in megabytes
	:-c --client connect to server from client		# -s, --server run in server mode, -D run as a daemon in the background
	:-r bidirectional test individually, use -d --dualtest to test simultaneously		# -c --client connect to server from client
			# -r bidirectional test individually, use -d --dualtest to test simultaneously
			</source>

	= References =		= References =
	*[http://binarynature.blogspot.co.uk/2013/03/measure-internet-connection-speed-from-linux-command-line.html Measure Internet Connection Speed from the Linux Command Line]		*[http://binarynature.blogspot.co.uk/2013/03/measure-internet-connection-speed-from-linux-command-line.html Measure Internet Connection Speed from the Linux Command Line]

Pio2pio: /* iperf */

2016-04-25T18:55:03Z

iperf

← Older revision		Revision as of 20:55, 25 April 2016
Line 52:		Line 52:
	:-M, --mss set TCP maximum segment size (MTU - 40 bytes)		:-M, --mss set TCP maximum segment size (MTU - 40 bytes)
	:-f m displays results in megabytes		:-f m displays results in megabytes
	:-s ~~start~~ server, -D ~~switch to~~ run it as a daemon in the background		:-s, --server run in server mode, -D run as a daemon in the background
	:-c --client connect to server from client		:-c --client connect to server from client
	:-r bidirectional test individually, use -d --dualtest to test simultaneously		:-r bidirectional test individually, use -d --dualtest to test simultaneously

Pio2pio: /* iperf */

2016-04-25T18:53:42Z

iperf

← Older revision		Revision as of 20:53, 25 April 2016
Line 37:		Line 37:
	This measures the bandwidth between two locations where one is set as a server and another as a client.		This measures the bandwidth between two locations where one is set as a server and another as a client.

	Start up server listening on port 8888. By default it is TCP port 5001 and TCP window size 64.0KB.		Start up server listening on port 8888. By default it is TCP port 5001 and TCP window size 64.0KB
	/opt/systems/bin/iperf -s -p 8888		/opt/systems/bin/iperf -s -p 8888

Line 44:		Line 44:

	Switches:		Switches:
	:-t option used in the above command tells to transfer data for X seconds		:-t option used in the above command tells to transfer data for X seconds
	~~:-p will tell the client to connect the port 8888 on the server~~
	~~:-w will specify your desired window size value~~
	~~:-u options needs to be also used on the client side for specifying UDP traffic in case server <code>iperf -s -u</code> was used~~
	:-P divide results into X time frames aka lines printed		:-P divide results into X time frames aka lines printed
			:-p --port server port to listen on/connect to
			:-w desired window size value
			:-l, --len length of buffer to read or write (default 8 KB)
			:-u --udp use UDP rather than TCP
			:-M, --mss set TCP maximum segment size (MTU - 40 bytes)
	:-f m displays results in megabytes		:-f m displays results in megabytes
			:-s start server, -D switch to run it as a daemon in the background
			:-c --client connect to server from client
			:-r bidirectional test individually, use -d --dualtest to test simultaneously

	= References =		= References =
	*[http://binarynature.blogspot.co.uk/2013/03/measure-internet-connection-speed-from-linux-command-line.html Measure Internet Connection Speed from the Linux Command Line]		*[http://binarynature.blogspot.co.uk/2013/03/measure-internet-connection-speed-from-linux-command-line.html Measure Internet Connection Speed from the Linux Command Line]

Pio2pio: Pio2pio moved page Internet speed via Terminal to Internet speed test using Terminal: More appropiate subject

2016-04-25T18:34:54Z

Pio2pio moved page Internet speed via Terminal to Internet speed test using Terminal: More appropiate subject

← Older revision	Revision as of 20:34, 25 April 2016
(No difference)

Pio2pio: /* Speedtest.net */

2015-03-12T20:50:37Z

Speedtest.net

← Older revision		Revision as of 22:50, 12 March 2015
Line 1:		Line 1:
	= Speedtest.net =		= Speedtest.net =
			<source lang=bash>
	sudo apt-get install python-pip		sudo apt-get install python-pip
	pip install speedtest-cli		pip install speedtest-cli
			</source>
	or:		or:
			<source lang=bash>
	sudo apt-get install python-setuptools		sudo apt-get install python-setuptools
	easy_install speedtest-cli		sudo easy_install speedtest-cli
			</source>
			This 2nd solution worked on AWS Ubuntu 13.04 Server and it needed ~3Mb (<tt>python-setuptools</tt>) to download versus ~80Mb for <tt>python-pip</tt>

	~~This 2nd solution worked~~ on ~~AWS Ubuntu 13~~.~~04 Server and it needed ~3Mb~~ (~~<tt>python-setuptools</tt>~~) to download ~~versus ~80Mb for <tt>python-pip~~</tt>		Run the speedtest:
			<source lang=bash>
			$ speedtest-cli
			Retrieving speedtest.net configuration...
			Retrieving speedtest.net server list...
			Testing from Global Crossing (217.156.150.69)...
			Selecting best server based on latency...
			Hosted by Gigaclear PLC (Slough) [8.91 km]: 13.461 ms
			Testing download speed........................................
			Download: 23.93 Mbit/s
			Testing upload speed..................................................
			Upload: 12.27 Mbit/s
			</source>

	= Wget =		= Wget =

Pio2pio: /* Wget */

2014-06-05T19:36:56Z

Wget

← Older revision		Revision as of 21:36, 5 June 2014
Line 9:		Line 9:

	= Wget =		= Wget =

	wget --output-document=/dev/null http://speedtest.wdc01.softlayer.com/downloads/test500.zip		wget --output-document=/dev/null http://speedtest.wdc01.softlayer.com/downloads/test500.zip
			wget -O /dev/null http://speedtest.sea01.softlayer.com/downloads/test100.zip
			curl -o /dev/null http://speedtest.sea01.softlayer.com/downloads/test100.zip

			wget -O /dev/null http://ipv4.download.thinkbroadband.com/1GB.zip
			wget -O /dev/null http://ipv4.download.thinkbroadband.com:81/1GB.zip
			wget -O /dev/null http://ipv4.download.thinkbroadband.com:8080/1GB.zip

	= iperf =		= iperf =

Pio2pio: /* Wget */

2014-03-07T14:28:56Z

Wget

@@ Line 11: / Line 11: @@
   wget --output-document=/dev/null http://speedtest.wdc01.softlayer.com/downloads/test500.zip
 = References =
 *[http://binarynature.blogspot.co.uk/2013/03/measure-internet-connection-speed-from-linux-command-line.html Measure Internet Connection Speed from the Linux Command Line]

Pio2pio: /* Speedtest.net */

2014-02-03T23:19:18Z

Speedtest.net

← Older revision		Revision as of 01:19, 4 February 2014
Line 1:		Line 1:
	= Speedtest.net =		= Speedtest.net =
			sudo apt-get install python-pip
	pip install speedtest-cli		pip install speedtest-cli
	or:		or:
			sudo apt-get install python-setuptools
	easy_install speedtest-cli		easy_install speedtest-cli

			This 2nd solution worked on AWS Ubuntu 13.04 Server and it needed ~3Mb (<tt>python-setuptools</tt>) to download versus ~80Mb for <tt>python-pip</tt>

	= Wget =		= Wget =