Overrides the default value for the number of threads that applications may spawn.
SERVERTHREADS [application_name] n
application_name—Optional. If you specify an application, all the databases in that application are affected by the SERVERTHREADS setting. If you leave out the application name parameter, the setting applies to the entire Essbase Server.
n—The number of threads the application may produce:
Between 20 and 500 on 32-bit platforms.
Between 20 and 1024 on 64-bit platforms.
Specify an integer between 20 and the maximum, inclusive. If you use the .CFG setting to specify a number lower than 20, it is interpreted as 20. If you use the .CFG setting to specify a number higher than the maximum, it is interpreted as 500 (on 32-bit platforms), or 1024 (on 64-bit platforms).
See Notes below.
SERVERTHREADS overrides the default value for the number of threads that application processes may spawn. The default value is defined by the number of licensed ports. Use this setting to make the maximum number of threads higher than the default value. See Notes.
When a transaction is requested, the application assigns a thread to the transaction and releases the thread when the transaction is complete.
The default value of SERVERTHREADS depends on the number of available ports on the Essbase Server. Note that one additional port is available for the system administrator, so that for 5 licensed ports, 6 available ports are shown when you type PORTS in the Agent window.
5 or fewer ports—5 default threads
6 to 11 ports—10 default threads
11 or more ports—20 default threads
Although the actual maximum value you can set is 500 (or 1024 on 64-bit platforms), the maximum number of threads an operating system can handle might be much lower. It is strongly recommended that you use the default value. If you want to set this parameter to a value higher than the default, check with your system administrator, as higher values can significantly consume system resources.
If your Essbase Server computer freezes while running multiple reports at the same time, increase the value of SERVERTHREADS by one for each report you run.
Each server thread may create child threads for tasks such as parallel calculation, parallel data load or export, and parallel restructuring. If the total number of running threads is too high, threads may lose efficiency in contending for server resources. To control the issue of thread contention, you can use the MAXTOTALACTIVETRANSACTIONS and MAXACTIVEUPDATETRANSACTIONS settings.
SERVERTHREADS 25
Allows all applications to spawn up to 25 threads.
SERVERTHREADS Sample 100
Allows the Sample application to spawn up to 100 threads.