Iperf Speed Testing - Revision history

imported>Schoen.kevin at 17:11, 10 February 2024

2024-02-10T17:11:13Z

imported>Schoen.kevin: /* Speed Test Software, Websites and Issues with Getting Accurate data */

2024-02-10T17:06:43Z

Speed Test Software, Websites and Issues with Getting Accurate data

← Older revision		Revision as of 17:06, 10 February 2024
Line 28:		Line 28:

	'''iperf -c iperf.acd.net -P 10 -t 240 -w 130000 -r'''		'''iperf -c iperf.acd.net -P 10 -t 240 -w 130000 -r'''


			'''iperf -c iperf.acd.net -P 10 -t 100000 -d'''

	== Servers on ACD.net's Network Configured for iperf ==		== Servers on ACD.net's Network Configured for iperf ==

imported>Schoen.kevin: /* Installing Iperf */

2013-07-25T13:49:06Z

Installing Iperf

← Older revision		Revision as of 13:49, 25 July 2013
Line 34:		Line 34:

	== Installing Iperf ==		== Installing Iperf ==
			Here is the best place to get the latest software: http://iperf.fr/

	*[[File:Iperf.zip]]		*[[File:Iperf.zip]]
	Download IPerf, unrar and install into '''c:\iperf\'''		Download IPerf, unrar and install into '''c:\iperf\'''

	*for a compiled version of iperf go here: http://www.mayoxide.com/iperf/

	For Windows XP and Windows 7, all you need to do is unzip the files and move them to your newly created iperf directory(folder).		For Windows XP and Windows 7, all you need to do is unzip the files and move them to your newly created iperf directory(folder).

imported>Allswede.tim at 16:16, 16 January 2013

2013-01-16T16:16:40Z

← Older revision		Revision as of 16:16, 16 January 2013
Line 21:		Line 21:
	=== Recommended Settings for Testing ===		=== Recommended Settings for Testing ===

	This command will run 10 parallel client threads over 240 seconds (4min).		This command will run 10 parallel client threads over 240 seconds (4min) with a TCP window size of 127K.

	'''iperf -c iperf.acd.net -P 10 -t 240'''		'''iperf -c iperf.acd.net -P 10 -t 240 -w 130000'''

			his command will run 10 parallel client threads over 240 seconds (4min) with a TCP window size of 127K - first upload then download test.

			'''iperf -c iperf.acd.net -P 10 -t 240 -w 130000 -r'''

	== Servers on ACD.net's Network Configured for iperf ==		== Servers on ACD.net's Network Configured for iperf ==

imported>Schoen.kevin: /* Run Iperf and performing initial testing */

2012-09-18T20:26:55Z

Run Iperf and performing initial testing

← Older revision		Revision as of 20:26, 18 September 2012
Line 47:		Line 47:
	==Run Iperf and performing initial testing==		==Run Iperf and performing initial testing==

	Run your iperf testing(iperf -c iperf.acd.net -P 10 -t 240)		Run your iperf testing:
			*iperf -c iperf.acd.net -P 10 -t 240

	<pre>C:\Users\henry.joshua.ACDINTERNAL>cd c:\iperf		<pre>C:\Users\henry.joshua.ACDINTERNAL>cd c:\iperf

imported>Schoen.kevin: /* Installing Iperf */

2012-09-18T20:26:21Z

Installing Iperf

← Older revision		Revision as of 20:26, 18 September 2012
Line 32:		Line 32:
	*[[File:Iperf.zip]]		*[[File:Iperf.zip]]
	Download IPerf, unrar and install into '''c:\iperf\'''		Download IPerf, unrar and install into '''c:\iperf\'''

			*for a compiled version of iperf go here: http://www.mayoxide.com/iperf/

	For Windows XP and Windows 7, all you need to do is unzip the files and move them to your newly created iperf directory(folder).		For Windows XP and Windows 7, all you need to do is unzip the files and move them to your newly created iperf directory(folder).
Line 42:		Line 44:

	Open a command prompt(Win>Run>cmd) and change directories(cd) to the C drive(c:\) under the iperf directory(c:\iperf)		Open a command prompt(Win>Run>cmd) and change directories(cd) to the C drive(c:\) under the iperf directory(c:\iperf)

			==Run Iperf and performing initial testing==

	Run your iperf testing(iperf -c iperf.acd.net -P 10 -t 240)		Run your iperf testing(iperf -c iperf.acd.net -P 10 -t 240)

imported>Henry.joshua: /* Installing Iperf */

2012-07-14T21:05:16Z

Installing Iperf

@@ Line 32: / Line 32: @@
 *[[File:Iperf.zip]]
 Download IPerf, unrar and install into '''c:\iperf\'''
 == Getting Started ==

imported>Henry.joshua at 23:48, 10 July 2012

2012-07-10T23:48:35Z

← Older revision		Revision as of 23:48, 10 July 2012
Line 207:		Line 207:

	This argument would transfer data to the server for 20 seconds (-t 20), and display the data in intervals of 2 seconds (-i 2)		This argument would transfer data to the server for 20 seconds (-t 20), and display the data in intervals of 2 seconds (-i 2)

			=== Complete List of Options/Arguments/Flags ===
			This is a complete list of the arguments for testing with Iperf.

			<pre>C:\iperf>iperf --help
			Usage: iperf [-s\|-c host] [options]
			iperf [-h\|--help] [-v\|--version]

			Client/Server:
			-f, --format [kmKM] format to report: Kbits, Mbits, KBytes, MBytes
			-i, --interval # seconds between periodic bandwidth reports
			-l, --len #[KM] length of buffer to read or write (default 8 KB)
			-m, --print_mss print TCP maximum segment size (MTU - TCP/IP header)
			-o, --output <filename> output the report or error message to this specified file
			-p, --port # server port to listen on/connect to
			-u, --udp use UDP rather than TCP
			-w, --window #[KM] TCP window size (socket buffer size)
			-B, --bind <host> bind to <host>, an interface or multicast address
			-C, --compatibility for use with older versions does not sent extra msgs
			-M, --mss # set TCP maximum segment size (MTU - 40 bytes)
			-N, --nodelay set TCP no delay, disabling Nagle's Algorithm
			-V, --IPv6Version Set the domain to IPv6

			Server specific:
			-s, --server run in server mode
			-D, --daemon run the server as a daemon
			-U, --single_udp run in single threaded UDP mode
			-R, --remove remove service in win32

			Client specific:
			-b, --bandwidth #[KM] for UDP, bandwidth to send at in bits/sec
			(default 1 Mbit/sec, implies -u)
			-c, --client <host> run in client mode, connecting to <host>
			-d, --dualtest Do a bidirectional test simultaneously
			-n, --num #[KM] number of bytes to transmit (instead of -t)
			-r, --tradeoff Do a bidirectional test individually
			-t, --time # time in seconds to transmit for (default 10 secs)
			-F, --fileinput <name> input the data to be transmitted from a file
			-I, --stdin input the data to be transmitted from stdin
			-L, --listenport # port to recieve bidirectional tests back on
			-P, --parallel # number of parallel client threads to run
			-T, --ttl # time-to-live, for multicast (default 1)
			-Z, --linux-congestion <algo> set TCP congestion control algorithm (Linux only)

			Miscellaneous:
			-x, --reportexclude [CDMSV] exclude C(connection) D(data) M(multicast) S(settings) V(server) reports
			-y, --reportstyle C report as a Comma-Separated Values
			-h, --help print this message and quit
			-v, --version print version information and quit

			[KM] Indicates options that support a K or M suffix for kilo- or mega-

			The TCP window size option can be set by the environment variable
			TCP_WINDOW_SIZE. Most other options can be set by an environment variable
			IPERF_<long option name>, such as IPERF_BANDWIDTH.</pre>

imported>Schoen.kevin: /* Server Setup (Windows) */

2012-04-08T14:41:14Z

Server Setup (Windows)

← Older revision		Revision as of 14:41, 8 April 2012
Line 39:		Line 39:
	=== Server Setup (Windows) ===		=== Server Setup (Windows) ===

	If you are testing to the ACD server, you do not need to install your own server.		If you are testing to the ACD server (iperf.acd.net), you do not need to install your own server. If you are planning on running your own server; the servers should not have a lot of other applications or software or active usage to get test results.

	To begin transmitting files between two locations, one machine must be designated the server, while the other must be the client. The command to designate one machine as the server is as follows:		If you are going to run your own server; To begin transmitting files between two locations, one machine must be designated the server, while the other must be the client. The command to designate one machine as the server is as follows:
	iperf -s		iperf -s

Line 50:		Line 50:
	TCP window size: 8.00 KByte (default)		TCP window size: 8.00 KByte (default)

	This setup is useful for creating a temporary iperf server for an iperf client to test to. It does not, however, set up a persistent server that will be up and online automatically whenever the machine is.		This setup is useful for creating a temporary iperf server for an iperf client to test to. It does not, however, set up a persistent server that will be up and online automatically whenever the machine is.

	=== Client Setup (Windows) ===		=== Client Setup (Windows) ===

imported>Schoen.kevin: /* Speed Test Software, Websites and Issues with Getting Accurate data */

2012-04-08T14:39:52Z

Speed Test Software, Websites and Issues with Getting Accurate data

← Older revision		Revision as of 14:39, 8 April 2012
Line 13:		Line 13:
	== Speed Test Software, Websites and Issues with Getting Accurate data ==		== Speed Test Software, Websites and Issues with Getting Accurate data ==

	There are many types of speed test softwares. ~~Speed~~ testing websites is inherently innaccurate ~~due to the complex nature of Internet~~, and ~~other processing interference issues~~. While sometimes usesful, websites such as www.speedtest.net and speedtest.acd.net will not provide accurate speed results on many types of connections, including wifi, bonded T1 lines, and many EFM services. ~~In addtion these~~ sites will not provide accurate speeds for services faster than 40-100mb/s.		There are many types of speed test softwares, with varying degrees of accuracy. Additionally, there are speed testing websites, these websites are inherently innaccurate, and do not provide a scientific or reliable data for troubleshooting. While sometimes usesful, websites such as http://www.speedtest.net and http://speedtest.acd.net (which is part of the speedtest.net network of server) will not provide accurate speed results on many types of connections, including wifi, bonded T1 lines, and many EFM services. Although ACD participates in speedtesting websites such as speedtest.net thier usufullness is limited. These sites will not provide accurate speeds for services faster than 40-100mb/s.

	ACD uses IPerf as the standard software for doing performance testing. For debugging purposes, ACD only uses Iperf. We do not rely upon random "speed test" websites for debugging purposes.		ACD uses IPerf as the standard software for doing all performance testing. For debugging purposes, ACD only uses Iperf. We do not rely upon random "speed test" websites for debugging purposes.

	Changing variables within Iperf also change the performance results, often quite dramatically. Based upon our lab results, please provide us data with the <b>Recommended Settings for Testing</b> below. Data without the recommended settings and time stamps will generally not be taken into account for troubleshooting.		Changing variables within Iperf also change the performance results, often quite dramatically. Based upon our lab results, please provide us data with the <b>Recommended Settings for Testing</b> below. Data without the recommended settings and time stamps will generally not be taken into account for troubleshooting.