OVMS3-idf/examples/wifi/iperf
2019-07-08 09:16:06 +08:00
..
components/iperf examples: fix iperf exit error 2019-04-22 12:14:21 +08:00
main Rename Kconfig options (components/esp32) 2019-05-21 09:09:01 +02:00
CMakeLists.txt ci: support to build esp32s2beta simple examples 2019-07-08 09:16:06 +08:00
iperf_test.py test: save throughput result to junit report 2019-04-19 14:39:44 +08:00
Makefile ethernet: add iperf example to test real bandwidth 2018-10-08 09:51:17 +08:00
README.md docs: udpate wifi document 2019-01-03 13:46:16 +08:00
sdkconfig.defaults Rename Kconfig options (components/esptool_py) 2019-05-21 09:32:55 +02:00
sdkconfig.defaults.00 Rename Kconfig options (components/esp32) 2019-05-21 09:09:01 +02:00
sdkconfig.defaults.01 Rename Kconfig options (components/esp32) 2019-05-21 09:09:01 +02:00
sdkconfig.defaults.02 Rename Kconfig options (components/esp32) 2019-05-21 09:09:01 +02:00
sdkconfig.defaults.03 Rename Kconfig options (components/esp32) 2019-05-21 09:09:01 +02:00
sdkconfig.defaults.04 Rename Kconfig options (components/esp32) 2019-05-21 09:09:01 +02:00
sdkconfig.defaults.05 Rename Kconfig options (components/esptool_py) 2019-05-21 09:32:55 +02:00
sdkconfig.defaults.06 Rename Kconfig options (components/esptool_py) 2019-05-21 09:32:55 +02:00
sdkconfig.defaults.07 Rename Kconfig options (components/esptool_py) 2019-05-21 09:32:55 +02:00
sdkconfig.defaults.99 Rename Kconfig options (components/esptool_py) 2019-05-21 09:32:55 +02:00
test_report.py examples: Fix Python coding style 2018-12-06 09:34:33 +01:00

Iperf Example

Note about iperf version

The iperf example doesn't support all features in standard iperf. It's compitable with iperf version 2.x.

Note about 80MHz flash frequency

The iperf can get better throughput if the SPI flash frequency is set to 80MHz, but the system may crash in 80MHz mode for ESP-WROVER-KIT. Removing R140R145 from the board can fix this issue. Currently the default SPI frequency is set to 40MHz, if you want to change the SPI flash frequency to 80MHz, please make sure R140R145 are removed from ESP-WROVER-KIT or use ESP32 DevKitC.

Introduction

This example implements the protocol used by the common performance measurement tool iPerf. Performance can be measured between two ESP32s running this example, or between a single ESP32 and a computer running the iPerf tool

Demo steps to test station TCP Tx performance:

  1. Build the iperf example with sdkconfig.defaults, which contains performance test specific configurations

  2. Run the demo as station mode and join the target AP sta ssid password

  3. Run iperf as server on AP side iperf -s -i 3

  4. Run iperf as client on ESP32 side iperf -c 192.168.10.42 -i 3 -t 60

The console output, which is printed by station TCP RX throughput test, looks like:

esp32> sta aptest

I (5325) iperf: sta connecting to 'aptest'

esp32> I (6017) event: ip: 192.168.10.248, mask: 255.255.255.0, gw: 192.168.10.1

esp32> iperf -s -i 3 -t 1000

I (14958) iperf: mode=tcp-server sip=192.168.10.248:5001, dip=0.0.0.0:5001, interval=3, time=1000

Interval Bandwidth

esp32> accept: 192.168.10.42,62958

0- 3 sec 8.43 Mbits/sec

3- 6 sec 36.16 Mbits/sec

6- 9 sec 36.22 Mbits/sec

9- 12 sec 36.44 Mbits/sec

12- 15 sec 36.25 Mbits/sec

15- 18 sec 24.36 Mbits/sec

18- 21 sec 27.79 Mbits/sec

Steps to test station/soft-AP TCP/UDP RX/TX throughput are similar as test steps in station TCP TX.

See the README.md file in the upper level 'examples' directory for more information about examples.