WindowsGuestDrivers/kvmnet/test and results - Revision history

Yan at 12:04, 10 August 2009

2009-08-10T12:04:42Z

← Older revision		Revision as of 08:04, 10 August 2009
Line 3:		Line 3:
	----		----

	Before performing benchmarks - configure [[WindowsGuestDrivers/kvmnet/registry\|~~windows~~ parameters]]		Before performing benchmarks - configure [[WindowsGuestDrivers/kvmnet/registry\|Windows parameters]]

	= Tests =		= Tests =

Yan at 12:04, 10 August 2009

2009-08-10T12:04:22Z

← Older revision		Revision as of 08:04, 10 August 2009
Line 3:		Line 3:
	----		----

	Before performing benchmarks - configure [[~~http://www.linux-kvm.org/page/~~WindowsGuestDrivers/kvmnet/registry\|windows parameters]]		Before performing benchmarks - configure [[WindowsGuestDrivers/kvmnet/registry\|windows parameters]]

	= Tests =		= Tests =

Yan at 12:03, 10 August 2009

2009-08-10T12:03:49Z

← Older revision		Revision as of 08:03, 10 August 2009
Line 1:		Line 1:
	'''Performance tests and results'''		'''Performance tests and results'''

			----

	Before performing benchmarks - configure [[http://www.linux-kvm.org/page/WindowsGuestDrivers/kvmnet/registry\|windows parameters]]		Before performing benchmarks - configure [[http://www.linux-kvm.org/page/WindowsGuestDrivers/kvmnet/registry\|windows parameters]]

Yan at 12:03, 10 August 2009

2009-08-10T12:03:25Z

← Older revision		Revision as of 08:03, 10 August 2009
Line 1:		Line 1:
	'''Performance tests and results'''		'''Performance tests and results'''
			Before performing benchmarks - configure [[http://www.linux-kvm.org/page/WindowsGuestDrivers/kvmnet/registry\|windows parameters]]

	= Tests =		= Tests =

Yan at 12:00, 10 August 2009

2009-08-10T12:00:33Z

← Older revision		Revision as of 08:00, 10 August 2009
Line 21:		Line 21:
	* [http://www.microsoft.com/whdc/device/network/TCP_tool.mspx How to Use NTttcp to Test Network Performance]		* [http://www.microsoft.com/whdc/device/network/TCP_tool.mspx How to Use NTttcp to Test Network Performance]
	* Cons: Windows only tool		* Cons: Windows only tool

			= Results =
			TBD

Yan at 11:58, 10 August 2009

2009-08-10T11:58:33Z

← Older revision		Revision as of 07:58, 10 August 2009
Line 2:		Line 2:

	= Tests =		= Tests =
	== Tools ~~uses~~ for performance tests ==		== Tools used for performance tests ==
	=== iperf ===		=== iperf ===
	* [http://www.noc.ucf.edu/Tools/Iperf/ Download]		* [http://www.noc.ucf.edu/Tools/Iperf/ Download]
Line 14:		Line 14:
	* Cons: No control over TCP windows. Windows version doesn't have some of the Linux version feature. Windows server should be restarted after each test.		* Cons: No control over TCP windows. Windows version doesn't have some of the Linux version feature. Windows server should be restarted after each test.

	=== Additional ~~tools~~ ====		==== Additional scripts ====
	* ~~Under~~ netkvm\tests\netperf_wrapper.rb - the scrip will run netperf according to its configuration (by default running 3 times for each message size and iterating message sizes between 32byte to 16K).		* netkvm\tests\netperf_wrapper.rb - the scrip will run netperf according to its configuration (by default running 3 times for each message size and iterating message sizes between 32byte to 16K).
			* netkvm\tests\netperf_log_parser.rb - parsing raw netperf output

			=== NTttcp ===
			* [http://www.microsoft.com/whdc/device/network/TCP_tool.mspx How to Use NTttcp to Test Network Performance]
			* Cons: Windows only tool

Yan at 11:54, 10 August 2009

2009-08-10T11:54:21Z

New page

'''Performance tests and results'''

= Tests =
== Tools uses for performance tests ==
=== iperf ===
* [http://www.noc.ucf.edu/Tools/Iperf/ Download]
* Typical command line: iperf -c <IP> -w <TCP window size>
* Pros: ability to control the TCP window size from command line and intermidiate results printouts during the test.
* Cons: High CPU consumption on Linux machines.

=== netperf ===
* [http://www.netperf.org/netperf/DownloadNetperf.html Download]
* Typical command line: netperf -H <IP> -l <test length> -- -m <message size>
* Cons: No control over TCP windows. Windows version doesn't have some of the Linux version feature. Windows server should be restarted after each test.

=== Additional tools ====
* Under netkvm\tests\netperf_wrapper.rb - the scrip will run netperf according to its configuration (by default running 3 times for each message size and iterating message sizes between 32byte to 16K).