Because processes on 64-bit have greatly increased memory addressability over 32-bit processes, the 64-bit edition of Essbase can handle larger outlines and cache sizes than 32-bit Essbase. In computing environments that support it, implementing 64-bit Essbase can improve the performance of existing applications and can sustain much larger applications. For information on platform support for 64-bit Essbase, see the Oracle Hyperion Enterprise Performance Management System Certification Matrix (http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html).
On 64-bit Essbase, you can set cache sizes larger than the existing 32-bit limits. In Essbase clients, the maximum values you can set for the data cache, data file cache, and index cache is 4 GB. You can enable larger values for the data cache and data file cache using the MEMSCALINGFACTOR configuration setting. See the Oracle Essbase Technical Reference.
The maximum thread settings are higher for 64-bit Essbase than for 32-bit Essbase. Table 169 lists the maximum thread settings for each. For information about changing thread settings, see the Oracle Essbase Technical Reference. For information about multi-threading, see Multithreading.
Default retrieval buffer settings for 64-bit Essbase are higher than for 32-bit Essbase. Table 170 lists the default retrieval buffer settings for each. See Changing Buffer Size.
Because of internal data structure size changes, 64-bit Essbase requires a larger retrieval sort buffer size than 32-bit Essbase. If you encounter the error, "Sort buffer limit of [x] rows have been exceeded" (where x is the current maximum number of rows allowed for the current buffer size), increase the retrieval sort buffer size by a factor of two. |