For an expected number of peak concurrent (active) users, P, set the following parameters.
|Parameter||Default Value||Recommended Value||Example|
|P / 15, rounded up to the nearest integer, minimum of 2||for P = 40, set to |
|5 * |
webapp.numProcesses = 3, set to
|P / 50, rounded up to the nearest integer, minimum of 2||for P = 225, set to |
Other applicable parameters
NOTE: Avoid modifying these parameters unless instructed by .
Limit Application Memory Utilization
services allow limitations on memory utilization by varying their JVM configuration's
value. These can be limited by modifying the following parameters:
Other services have low memory requirements.
Jobs run on mthe
and "Quick Scan" samples are executed by the Photon running environment embedded on the
, running alongside the application itself. Two main parameters can be used to tune concurrency of job execution and throughput of individual jobs:
|Maximum number of simultaneous Photon processes; once exceeded, jobs are queued|
|Number of threads used by each Photon process||4|
Increasing the number of concurrent processes allows more users' jobs to execute concurrently. However, it also leads to resource contention among the jobs and the application services.
Photon's execution is purely in memory. It does not spill to disk when the total data size exceeds available memory. As a result, you should configure limits on Photon's memory utilization. If a job exceeds the configured memory threshold, it is killed by a parent process tasked with monitoring the job.
true to enable the monitor, and set to
false (limited only by operating system) otherwise
|Percentage of available system memory that each Photon process can use (if |
A reasonable rule of thumb: the input data size should not exceed one tenth of the job’s memory limit. This rule of thumb accounts for joins and pivots and other operations that can increase memory usage over the data size. However, this parameter is intended as a safeguard; it is unlikely that all running jobs would approach the memory limit simultaneously. So you should "oversubscribe" and use slightly more than
batchserver.workers.photon.max) for this threshold.
In addition to a memory threshold, execution time of any Photon job can also be limited via the following parameters:
true to enable the timeout, and set to
false (unlimited) otherwise
|Time in minutes after which to kill the Photon process (if |
For more information, see Configure Photon Running Environment.