WCS Stress Test

[ksko]

Hello, guys

While looking for WebRTC support servers, I came across WCS5 and tried to test it.
I installed WCS on Amazon EC2 and Standalone(30 day license).

I've checked the demo apps, and I'd like to do a load test.

I'm following the documents below, but they don't seem to be working properly.
CPU, network traffic is not changing before and after the test.

From the log files, it looks like the installation is in order, but I don't know what the problem is.
Is the document valid?

WCS on Amazon EC2 : C4.large
Standalone : CPU E5-2620 * 2, 64G RAM
XORG : CPU E5-2620 * 2, 64G RAM

1. Server settings tests

Server settings tests  - Web Call Server 5.2 - EN - Flashphoner Documentation

docs.flashphoner.com

2. Load testing using another server

Load testing using another server - Web Call Server 5.2 - EN - Flashphoner Documentation

docs.flashphoner.com

 

[Max]

Good day.
Please read the following articles about load testing methods and samples
1. What kind of server do you need to run a thousand WebRTC streams?
2. Comparing load testing methods

 

[ksko]

Hello,
Thanks to you, I tested it.

We test 1,000 streams, and as you can see in the image below, it takes nearly 20 minutes to reach 1,000 after 900 streams, and after 1,000 streams, there is a problem where the CPU load rises rapidly.
publish : 1280x720
Traffic should be more than 2Gbps(at least 2mbps * 1000), but only up to 750Mbps and not increasing.

Do you have any idea why cpu, and traffic are fluctuating?

 

[Max]

WCS on Amazon EC2 : C4.large

C4.large (2 vCPU, 3.75 Gb RAM) is not enough for 1000 subscribers. You should use at least c5.4xlarge (16 vCPU, 32 Gb RAM, up to 10 Gb bandwidth). Also, the following tweaks should be applied:
1. WebRTC traffic encryption hardware acceleration enabled
2. Stream distribution optimization enabled
3. The tweaks listed in the article What kind of server do you need to run a thousand WebRTC streams?

 

[ksko]

I checked what you said again and tested it.

The test was not done on AWS, but on a standalone server.

WCS #1 : E5-2620 v4 * 2 (16 Core 32 Thread), 64Gb RAM, 32Gb Heap, 10Gb Fiber
WCS #2 : E5-2620 v4 * 2 (16 Core 32 Thread), 64Gb RAM, 32Gb Heap, 10Gb Fiber

2 Mixing publishing

HD(1280x720) publishing

Is there any way to solve the problem of nearly 300 CPU loads?

 

[Max]

Is there any way to solve the problem of nearly 300 CPU loads?

You can disable stream distribution optimization and enable traffic encryption in a separate thread for each client session. In this case, CPU load should be lower, but playback delay may grow.
So, if your target is minimal delay, consider more powerful CPU. If your target is CPU, you should accept some playback delay.

Mixing publishing

Please clarify: do you testing stream mixer? If yes, please read this fresh article How many mixers can a server have? because in this case CPU load is higher due to stream transcoding while mixing.

 

[ksko]

Please clarify: do you testing stream mixer? If yes, please read this fresh article How many mixers can a server have? because in this case CPU load is higher due to stream transcoding while mixing.

We are also considering MCU, but now focusing on live broadcasting.

CPU usage (50%) seems reasonable, but I can't figure it out why Load average goes up too high.

I attached 2453.jstack.txt, please give me a any hint why so high CPU Load Average.

 

[Max]

Replyed in this post.