WindowsGuestDrivers/kvmnet/test and results: Difference between revisions
From KVM
No edit summary |
No edit summary |
||
| (5 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
'''Performance tests and results''' | '''Performance tests and results''' | ||
---- | |||
Before performing benchmarks - configure [[WindowsGuestDrivers/kvmnet/registry|Windows parameters]] | |||
= Tests = | = Tests = | ||
== Tools | == 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 18: | ||
* 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 | ==== Additional scripts ==== | ||
* | * 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 | |||
= Results = | |||
TBD | |||
Latest revision as of 07:04, 10 August 2009
Performance tests and results
Before performing benchmarks - configure Windows parameters
Tests
Tools used for performance tests
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
- 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 scripts
- 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
- How to Use NTttcp to Test Network Performance
- Cons: Windows only tool
Results
TBD