119 | | === BWM-ng === |
120 | | For performance testing, you may want to run some bandwidth tests. Real-time bandwidth use can be monitored using BWM-ng. By default, the tool will monitor all interfaces on the Console. To just monitor the !OpenFlow interface, you must specify `eth1.100`. To output this to a csv, use the following command: |
| 119 | === Iperf === |
| 120 | For performance testing, you may want to run some bandwidth tests. iperf is a tool that measures maximum network performance using TCP for throughput and UDP for jitter and datagram loss. The standard image used for the Sandbox nodes when booted with command `omf tell on` comes with iperf. To take measurements, you need at least two nodes. One node becomes the server, the other(s), clients. |
| 121 | |
| 122 | To start the server: |
| 123 | {{{ |
| 124 | iperf -s |
| 125 | }}} |
| 126 | and on the client: |
| 127 | {{{ |
| 128 | iperf -c <server ip address> |
| 129 | }}} |
| 130 | |
| 131 | iperf, however, cannot take real-time bandwidth measurements. Real-time bandwidth use can be monitored using BWM-ng. |
| 132 | |
| 133 | === BWM-ng === |
| 134 | By default, the tool will monitor all interfaces on the Console. To monitor just the !OpenFlow interface, you must specify `eth1.100`. To output this to a csv, use the following command: |