If you use P2P connections, you can expect that some portion of these is over relay. We recommend running two Gateways behind a standard load balancer for redundancy purposes.įor MCU and SFU connections, relay is generally not required see STUN/TURN Use Cases. We run our demo environment Gateway on the equivalent of an AWS-EC2 c5.xlarge (4x CPU, 8 GB RAM), and it can handle thousands of concurrent clients. So, to handle the load described here, you would require at least four Media Servers in a clustered environment.Ī single Gateway can handle a lot more traffic than 320 concurrent connections. In general, you can expect one Media Server, on the equivalent of an AWS-EC2 c4.large (2x CPU, 4 GB RAM) instance, to handle ~100 concurrent connections in SFU mode with a standard 480p stream. Using 32,000 as a starting point means that we need to plan for 3,200 active users and 320 concurrent at any moment in time. It doesn't matter how many users you have, but it matters how many users you expect to have active at the same time.Īs a general best practice, concurrency is estimated using the 100:10:1 rule, which states that for every 1,000 named users, 100 are quite active, and about 10 are concurrent at any given point in time. How Many Server Instances Do You Need?Įstimating exactly the number of servers you need depends on expected concurrency. For client connections, allow inbound UDP traffic on ports 49152-65535 on public interfaces.įor SIP requests, allow UDP or TCP traffic on port 5061 on public interfaces.If the port 8445 is unavailable, Media servers try the next port incrementally until one is available. For clustering, allow TCP traffic on port 8445.Load balancer with high-availability guarantees.Allow inbound TCP traffic on port 8443 (default, configurable) for HTTPS.Allow inbound TCP traffic on port 8080 (default, configurable) for HTTP.The following specifications describe the hardware requirements for each LiveSwitch Server component. A SIP connector if your use case requires SIP interoperability.A cluster of Media Servers to handle your media traffic depending on your peak concurrent usage.At least two load-balanced Gateway Servers for redundancy.Set Up a Production Environmentįor production, we recommend that you set up the following: SIP Connector: Provides interoperability with third-party SIP services.įor development, you must set up at least one Gateway and one Media Server for your clients to get SFU or MCU connections.Media Server: Provides WebRTC connections allowing your clients to stream media through SFU or MCU connections.Gateway: Provides signaling capability allowing your clients to make connections to Media Servers.LiveSwitch Server consists of three server components:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |