...
Here, 8888 is the ID of the Java process.
Testing channel bandwidth using iperf
A stream published picture quality depends on channel bandwidth between publisher and server, the same for subscriber. Channel bandwidth can be checked using iperf utility. This program is implemented for all major OS: Windows, MacOS, Ubuntu/Debian, CentOS. iperf in server mode can be installed and running with WCS, that allows to check whole channel bandwith from publisher to viewer.
iperf can be installed on CentOS 7 as follows:
Code Block | ||||
---|---|---|---|---|
| ||||
yum install iperf3 |
Run iperf in server mode
Code Block | ||||
---|---|---|---|---|
| ||||
iperf3 -s -p 5201 |
where 5201 is iperf port for testing client connections
On client side iperf can be launched as follows:
1. To test upload channel bandwith (Windows example)
Code Block | ||||
---|---|---|---|---|
| ||||
iperf3.exe -c test2.flashphoner.com -p 5201 -w 256K |
Where
- test2.flashphoner.com - WCS server
- 5201 - iperf port to connect
- 256K - TCP buffer size
The result of the command above should look like this:
2. To test download channel bandwidth
Code Block | ||||
---|---|---|---|---|
| ||||
iperf3.exe -c test2.flashphoner.com -p 5201 -w 256K -R |
Where
- test2.flashphoner.com - WCS server
- 5201 - iperf port to connect
- 256K - TCP buffer size
The result of the command above should look like this:
By default, iperf tests the channel for 10 seconds. This interval should be increased, for example, to 120 second
Code Block | ||||
---|---|---|---|---|
| ||||
iperf3.exe -c test2.flashphoner.com -p 5201 -w 256K -t 120 |
Note that iperf major versions on server and on testing client should be the same. Today version 3 is actual, but ther is also version 2 in repositories.