To manage server resources, you can set limits for a number of
connection parameters. Limits set at the server level apply to all
of the publishing points on that server. You can set the limits for
the following parameters on the Properties tab:
Limit player connections. Sets the maximum number of
player connections.
Limit outgoing distribution connections. Sets the
maximum number of distribution
servers that can connect to this origin server.
Limit aggregate player bandwidth. Specifies the maximum
amount of bandwidth in kilobits per second (Kbps) that all player
connections can use.
Limit aggregate outgoing distribution bandwidth.
Specifies the maximum amount of bandwidth in Kbps that distribution
server connections can use.
Limit bandwidth per stream per player. Specifies the
maximum amount of bandwidth in Kbps that a single player connection
can use.
Limit bandwidth per outgoing distribution stream.
Specifies the maximum amount of bandwidth in Kbps that a single
distribution server connection can use.
Limit connection rate. Specifies the maximum number of
connection requests processed per second. The default value is
50.
Limit player timeout inactivity. Specifies the number of
seconds that a player can remain connected but inactive before
being automatically disconnected. The default value is 3,600
seconds (1 hour). This default value supports users pausing
playback of content for an extended period of time and then
restarting playback without having to reconnect to the server.
Limit connection acknowledgement. Specifies the number
of seconds that the server will wait for the player to respond to a
connection acknowledgement request before disconnecting the player.
Connection acknowledgement requests are sent to the player by the
server to verify the connection to the player. The default value is
60 seconds. If you are streaming in an environment with high
latency, consider increasing this value
to correspond with network conditions.
When a limit is reached, subsequent connection requests are
refused, and a limit hit event is displayed in the
Troubleshooting event list.
