Webrtc load testing using Chrome - slow processing

[Antonis Tsakiridis]

Hello, 

I'm trying some webrtc testing scenarios to stress our webrtc-enabled media server that involve multiple Chromium browser tabs being spawned (no Selenium involved) and receiving webrtc audio calls. I have noticed that while with 20 registered users (i.e. 20 tabs) calls are processed fine, when I increase the number to 50 I start getting issues. More specifically I see that gradually Chromium starts to take longer and longer to respond and from a point on the scenarios start to fail (without any apparent reason in the Chromium logs)

Notice that I'm using Chromium in headless Amazon EC2 instance (using Xvfb)

Any hints or ideas what might be triggering it? Do 50 tabs seem too many for a modern machine to cope with? (EC2 instance has 4 vCPUs, 2.5 GHz, Intel Xeon E5-2670v2, 15 GiB memory) 

Notice that I investigated whether the headless EC2 instance is overloaded, but doesn't seem to be so: no swapping, no excess waiting on I/O, memory and CPU consumption seem normal and well below 100% 

Thanks a lot in advance,

Antonis Tsakiridis

[Christoffer Jansson]

Without knowing the fine details it could be that the browser process is getting starved. My suggestion is to run several Chromium instances instead.

--

---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/CAM7er2PQH_m0nhXQ2YPVPpmr8wN88CH8YwKQd6NV868A4_Q6ZQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--

/Chris

[Antonis Tsakiridis]

Thanks for your answer Christoffer, but I couldn't find a way to truly keep separate Chromium instances. Seems that Chromium always somehow manages resources between instances and the boundaries are never clear. Do you have a specific invocation in mind?

[Christoffer Jansson]

That is true that they do share a single browser process if you open up new windows/tabs. In order to open a separate instance you need to specify a new profile via command line, start chromium with --user-data-dir=/tmp/user1. Then just repeat this with new profile directories for each new instance you want to start.

To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/a478a55f-3745-4d38-aed3-63596a05b3cf%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

/Chris

[Antonis Tsakiridis]

Hm, yeah I had thought of that earlier but seemed a bit more complex to handle in our framework. Anyway, thanks a lot. I'll write back if I manage to use that and get results

Best regards,

Antonis Tsakiridis

[Christoffer Jansson]

On Wed, Sep 7, 2016 at 1:51 PM Antonis Tsakiridis <antonis.t...@telestax.com> wrote:

Hm, yeah I had thought of that earlier but seemed a bit more complex to handle in our framework. Anyway, thanks a lot. I'll write back if I manage to use that and get results

This is what we do for our testing (i.e. ensure we have a clean profile) and most other test drivers like Webdriver etc.

Best regards,

Antonis Tsakiridis

--

---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/CAM7er2MT%2Bhi7n-KYRr%3DesWveOUKwXp3%3D4aDU2db%2BXEmAeA8S%2BQ%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--

/Chris