Installation guide

e maximum connection time using the above conguration is 4 hours. Aer 4 hours, the core

process is closed and all connections are dropped. At this stage, the client SWF le initiates a

reconnect routine that reestablishes the stream playback.

Changingthenumberofprocesses(numprocs)conguresthenumberofprocessesinwhich

connectionsaredistributed.Changingthenumprocssettingto2andusingthesamesettings

as before reduces the maximum connection time from 4 hours to 2 hours. Aer the second hour,

the MaxCores limit of 4 is reached. To spawn two more processes, the rst two processes are

killed, and the connections are closed.

<Scope>adaptor</Scope>

<Distribute numprocs=”2”>vhost</Distribute>

</LifeTime>

</Process>

Example of distributed process conguration

e maximum lifetime for connections in this conguration is 2 hours, because the MaxCore

limit is set to 4 and the numProcs is set to 2.

To calculate the maximum connection time for clients, use this formula:

(MaxCore DIV NumProcs) x Rollover

Example: (4 DIV 2) X 3600 = 7200 seconds (2 hours)

To calculate the total number of processes, use this formula:

Number of Scopes X NumProcs X MaxCores

Exampleusing<Distribute>adaptor</Distribute> with two adaptors:

2 X 2 X 4 = 16 Core processes

To calculate the amount of RAM required to support the distributed processes, multiply the total

numberofprocessesby4.Eachcoreprocesscanuseupto4GBofRAM;therefore,theprevious

examplewith16corescouldconsumeupto64GBofRAM.