In multi-Server Sites, system designers must consider the number of desktop clients and the number of devices available on each Media Server to avoid potential bottlenecks. While the software is highly efficient, hardware and network stack limits apply to concurrent connections.

Defining the maximum number of TCP connections per Media Server

The amount of concurrent Desktop clients that can connect to any Media Server is limited by the number of TCP connections the server process can support.

For the Media Server, the threshold is 2000 concurrent TCP connections per Media Server.

Calculating Capacity

Historically, we used a formula to estimate capacity. However, please note that these are estimates, as different client versions, plugins, and API calls can change the actual footprint.

• Initial Connection: ~5 TCP Connections (Message bus, API requests, etc.)
• Live Streams: 1 TCP Connection per device being viewed.
• API/Plugins: Additional calls or 3rd-party plugins may occupy extra slots in the pool.

Common scenarios for a single server:

• up to 333 Desktop Clients viewing 1 device each.

• up to 80 Desktop Clients viewing 20 devices each.

• up to 28 Desktop Clients viewing 64 devices each.

How to Check Current TCP Connections

Administrators can monitor the real-time load of any Server within a Site via the WebAdmin interface. 
To view these metrics:

1. Open your browser and log in to the WebAdmin interface of your Media Server.
2. Navigate to the Information tab at the top.
3. On the left sidebar, select Servers and click on the specific Server you wish to inspect.
4. Scroll down to the network section to find:
   • Incoming Connections: Connections from Clients, Cameras, or other Servers.
   • Outgoing Connections: Connections to Clients (video streams) or other Servers in the Site.
5. Total Load: The sum of Incoming and Outgoing connections represents your current utilization of the 2000-connection limit.