| 231 | | [http://iperf.sourceforge.net/ Iperf] can be used to generate network traffic. It has previously been used to tune OpenVPN performance: look [wiki:Gigabit_Networks_Linux here]. |
| | 231 | [http://iperf.sourceforge.net/ Iperf] can be used to generate network traffic. It has previously been used to tune OpenVPN performance: look [wiki:Gigabit_Networks_Linux here]. There are a few caveats when using iperf as described by Jason Haar ([http://thread.gmane.org/gmane.network.openvpn.user/33252/focus=33269 original message] on openvpn-users mailing list). |
| | 232 | |
| | 233 | {{{ |
| | 234 | FWIW iperf doesn't send random data - it's sends the ASCII sequence over |
| | 235 | and over again. i.e. it is "compressible" depending on what lies |
| | 236 | between. We have Riverbeds here and I was amazed how our 10Mbs WAN links |
| | 237 | suddenly jumped to 1Gbs according to iperf! Ended up the Riverbeds were |
| | 238 | able to do a lot of smoke-n-mirrors with iperf traffic |
| | 239 | |
| | 240 | You can run iperf as "iperf -c ser.ver.name -F /tmp/big.zip.file" so |
| | 241 | that it is actually sending (effectively) random data - in order to |
| | 242 | remove some of the potential tricks that could lie between your client |
| | 243 | and server. |
| | 244 | |
| | 245 | Also, "iperf -c ser.ver.name -P 4" is a good way of measuring BANDWIDTH |
| | 246 | instead of THROUGHPUT - which a standard single-channel TCP stream measures |
| | 247 | }}} |
