Thursday, November 7, 2013

Essbase Tuning For Planning Applications

Essbase Tuning For Planning Applications

Tuning Essbase for use with Planning in order to improve performance and avoid errors araising from a lack of resources when running Business Rules and Calculation Scripts.

The Folling are basic guidelines for Essbase tuning that are intended to cover the use of Essabse with Planning applications.

To Improve performance go through each of the suggested optimizations below and then test to see where the most progress is made. Always remember to back up your Essabse data before making any changes.

1. Block Size:
The recommended block size is between 8Kb and 100Kb. the only wat to alter block size is to change sparse dimensions to dense or vice versa. Changing a dense dimention to sparse will reduce block size and increate the overall number of blocks. See the Planning documentation for more information on setting dimensions to be dense or sparse.

2. Vertual Memory:
Recommended virual memory setting for Window sytems:
2 to 3 times the RAM Available. 1.5 times the RAM on older systems.

3. Chaches:

Index Cache:
Minimum: 1Mb
Default: 10 Mb
Recommended: combined size of all ESS*.IND files if possible;
otherwise as large as possible given the availbal RAM

DataFile Cache:
Minium: 8 Mb
Default: 32 Mb
Recommended: combined size of all ESS*.PAG files if possible;
Otherwise as large as possible given the available RAM, up to a maximum of 2GB.

Importent: The Data File Cache is not used if the database is buffered rather than direct I/O (Check the "Storage" tab). Since all Planning databases are buffered, and most customers use buffered for native Essbase apllications too, this cache setting is usually not relevant. the Data Cache is the setting that matters in most cases.

Data Cache:
Miniumum: 3 Mb
Default: 3 Mb
Recommended: 0.125 * combined size of all ESS*.PAG files, if possible, otherwise as large as possible given the available RAM.

Note: A useful indication of the health of the caches can be gained by looking at the "Hit Ratio" for the cache on the Statistics tab in EAS. 1.0 is the best possible ratio, lower means lower performance.

4. Disk Space:
The recommended disk space is a minimum of double the combined total of all .IND and .PAG files. You need double the space because you have to have room for a restructure, whcih will require twice the usal storage space whilst it is ongoing.

No comments:

Post a Comment