This results in decreased server load times.
Parameter type: optional, static
To run in multi-threaded mode, you must set MaximumCubeLoadThreads to the number of processor cores on the Planning Analytics database that you want to dedicate to cube loading and feeder processing.
Generally, the best performance is achieved when the parameter is set to a value equal to (number of available processor cores) - 1. For example, if the Planning Analytics database is running on a computer with four processor cores, MaximumCubeLoadThreads must be set to 3. This ensures that one processor core is available to run other applications while the Planning Analytics database is loading.
The maximum value for MaximumCubeLoadThreads is 32.
When MaximumCubeLoadThreads is set to 0, cube loading and feeder processing are not multi-threaded. This is the default behavior when MaximumCubeLoadThreads is not explicitly set in the Planning Analytics database configuration.
When MaximumCubeLoadThreads is enabled, the Planning Analytics database cannot manage the order in which feeders are calculated. There might be cases where processing order has an adverse effect on your application due to some order-of-evaluation dependencies in the multi-threaded environment.
If your Planning Analytics database uses conditional feeders where the condition clause contains a fed value, you must disable the use of multiple threads at load time. Set MaximumCubeLoadThreads=0 or exclude the parameter from the Planning Analytics database configuration.