Skip to end of metadata
Go to start of metadata


WebRTC stream pulling from another WCS server may be useful to load testing according to the following test scenario:

  1. Stream is published on server 1.
  2. Server 2 makes a specified number of Websocket connections (100 for example), as a standalone browser client.
  3. Server 2 pulls a specified number of copies of stream published on server 1, as a viewer.


1. For the test we use:

2. Open Console application over HTTP (not HTTPS!)

3. Install ACAO extension, allow Cross-Origin-Resource-Sharing

4. Enter server name and press 'Add node'. The server will be a subscriber which pulls streams. Then, add server which will be a stream source to test.

5. Open Two Way Streaming application, then publish the stream from web camera

6. Select in Console application, press 'Pull streams' button, set the test parameters:

  • Choose node - choose server to test
  • Local stream name, Remote stream name - set the stream published name
  • Qty - set the viewers quantity (100 for example)


7. Press 'Pull' button. The test begins.

8. Select server. The page displays a list of media sessions in which the published stream is played. Current server load information is displayed at top right corner.

CDN Edge server load testing

CDN Edge server load testing is performed by the following scenario:

  1. Streams are published on Origin server.
  2. Testing server makes a specified number of Websocket connections (100 for example) to Edge server, as a standalone browser client.
  3. Testing server pulls a specified number of copies of all the streams available to Edge server, as a viewer.

Quick manual on Edge server testing

1. For test we use:

2. Deploy CDN with the following server roles:

  • test1 - Origin
  • test2 - Edge

Add the foolowing parameter to Edge server settings


3. Open Console application over HTTP (not HTTPS!)

4. Allow Cross-Origin-Resource-Sharing

5. Enter Edge server name, press 'Add node'. This server will be tested. Add server similarly, this server will be a subscriber which pulls streams.

6. Open Two Way Streaming application, publish stream from web camera

7. Selet server in Console application, press 'Stress play stream', set the following test parameters:

  • Choose node - select server for testing
  • Choose test mode - select Random
  • CDN - set the checkbox
  • Max streams - set the number of viewers (100 for example)

7. Press 'Start'. The test begins.

RTMP pulling test

Since build 5.2.767 it is possible to pull streams via RTMP while testing. This can be enabled using the following parameter on testing server


In test configuration window, choose "Proto pull: RTMP" 

The test itself works like WebRTC test

Tuning recommendations

If the load test was failed, it is recommended to change the following setver settings.

1. In file extend range of UDP ports and disable fast streaming video decoder start:

media_port_from = 20000
media_port_to = 39999

2. In file extend heap memory limits. It is recommended to set the limit in half of physical RAM, for example, set 16 Gb while physical RAM is 32 Gb. Make sure you have enough RAM: 

-Xmx16g -Xms16g

Known issues

1. By default, no more than 1000 streams are pulled

Symptoms: if subscribers quantity set to more than 1000, only 998 streams are pulled

Solution: maximum agent ports number is limited to 999 by default:


To expand this limit, the following parameter should be increased


in file.