In terms of Business Rules and Calc Scripts – these are both ran by Essbase. Essbase can be tuned to take advantage of dual and / or quad core processors.
- Up to version 220.127.116.11 Essbase can use a maximum of 4 (integer between 1-4) CPU per Essbase application on 32 bit platforms when running calc parallel on a Block Storage application.
For Block Storage on 64-bit platforms, an integer between 1-8.
The default value, 1, specifies serial calculation: no parallel calculation takes place.
- From Version 18.104.22.168 on the limits have increased to:
BSO: up to 64 threads for 32 bit Installations and 128 threads for 64-bit Installations.
ASO: up to 128 threads for 32-bit OR 64-bit installs.
- Essbase (<= v 22.214.171.124.x) can use a maximum of 8 (integer from 1-8, default value 2) CPU per Essbase application when running calc parallel on an Aggregate Storage application (ASO).
- Essbase can use any number of CPU available when running queries.
Each running query however can only use one CPU.
- Essbase relies on the machine to actually assign the threads to different CPUs.
- Adding more CPUs to a machine should never hurt performance.
At the very least it should increase query concurrency on the machine as long as disk I/O doesn’t become a bottle neck.
- When more than 4 or 8 CPUs are available (depending on whether you are using ASO or BSO) Essbase can use these CPUs to make concurrent calculations on different applications faster as long as disk I/O doesn’t become a bottle neck.