Jitsi JVB 2 performance testing 2020

ya working on my repo

1 Like

Why are you changing port 9090 to other port ?

@congthang Typo here?

You removed port 9090 from here?

that what make it working lol

each JVB need it own jetty_port. as they are in the same kubernetes cluster and websocket is routing to the jvb connected.

colibri (JVB) websockets

location ~ ^/colibri-ws/([a-zA-Z0-9-\.\:]+)/(.*) {
    proxy_pass http://$1/colibri-ws/$1/$2$is_args$args;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
    tcp_nodelay on;
}
2 Likes

@congthang You can use metacontroller for dynamically generating service.yaml for jvb’s instead of creating one by one for all the jvb’s.

1 Like

Would be nice if you can contribute to repo

1 Like

Hi @congthang , Can you please tell what are the resolution and bitrates used for this benchmark testing? If you can provide the configuration (from config.js I believe) that will help. Thanks

Its from mvn test I think it very low