Distribute
Specifies how to distribute application instances to processes. The default value is insts, meaning each application instance runs in its own process. This tag contains a numprocs attribute, which specifies the maximum number of processes to run concurrently. The default value of the numprocs attribute is 3.
This feature is turned on by default. To use this feature, the numprocs attribute must be set to a value higher than 0 or 1. With the default configuration, for all your applications and application instances under a single virtual host, three core processes will run. Each virtual host is allotted three core processes, so systems that use multiple virtual hosts will generate more running processes. For more information, see Configure how applications are assigned to server processes.
Scopes have an enclosing relationship with a strict ordering: adaptors contain virtual hosts, which contain applications, which contain instances, which contain clients. The value of the Distribute tag must be a scope that is lower in order than the value in the Scope tag. In other words, if the value of Scope is adaptor, the value of Distribute can be vhosts, apps, insts, or clients. If the value of Scope is app, the value of Distribute can be insts or clients. By default, the server uses the value immediately lower than the one specified in the Scope tag.
The following table lists the values available for the Distribute element:
|
Value |
Description |
|---|---|
|
vhosts |
All instances of applications in a virtual host run together in a process. |
|
apps |
All instances of an application run together in a process. |
|
insts |
Each application instance runs in its own process. This is the default value. If you choose this value, you must also set the Distribute numprocs attribute to a value greater than 1. |
|
clients |
Each client connection runs in its own process. Use this value for stateless applications--applications that don't require clients to interact with other clients and don't have clients accessing live streams. Most vod (video on demand) applications are stateless because each client plays content independently of all other clients. Chat and gaming applications are not stateless because all clients share the application state. For example, if a shared chat application were set to client, the messages wouldn't reach everyone in the chat because they'd be split into separate processes. |
<Distribute numproc="1"></Distribute>
Send me an e-mail when comments are added to this page | Comment Report