HFM Application Server Registry Tuning
Default HFM Memory Settings
a. MaxNumDataRecordsinRAM
In general MaxNumDataRecordsinRAM is the most significant setting as it decides how many records to maintain in RAM.
HKEY_LOCAL_MACHINE\SOFTWARE\Hyperion Solutions\Hyperion Financial Management\Server
Value: MaxNumDataRecordsInRAM
Type: DWORD
Data: 1000000 (Decimal) (Default setting)
Important Note: When total number of records in RAM goes above this value, the FreeLRU is called to release records from memory to free up some memory for HFM server. The warning message“FreeLRUCachesIfMoreRAMIsNeeded released data cubes” is recorded in HsvEvent.log (located in HFM application server).
b. MinDataCacheSizeinMB
By setting this value at a higher number, you can reduce the number of DataCache growth attempts and hence reduce memory fragmentation. Typically DataCache is grown on a per need basis, and it will grow 25 MB maximum at a time.
HKEY_LOCAL_MACHINE\SOFTWARE\Hyperion Solutions\Hyperion Financial Management\Server
Value: MinDataCacheSizeInMB
Type: DWORD
Data: 130 (Decimal) (Default setting)
c. MaxDataCacheSizeinMB
The maximum amount of memory that HFM application server will allocate to store the cell values and cell status. If more memory is required by system then the cell value and cell status will be paged out to disk based on the LRU logic. Workaround is to increase the cache size.
HKEY_LOCAL_MACHINE\SOFTWARE\Hyperion Solutions\Hyperion Financial Management\Server
Value: MaxDataCacheSizeInMB
Type: DWORD
Data: 260 (Decimal) (Default setting)
Important Note: If performance of a consolidation operation decreases because of paging, you can increase MaxDataCacheSizeInMB to minimize paging. This value should be more than the total memory usage allowed by “MaxNumDataRecordsInRAM”, so that system does not page out the cells unnecessarily to disk. Too low MaxDataCacheSizeInMB setting means that you will run out of memory to store data records and begin paging, which reduces system performance.
HFM 32 BIT Memory Settings for Larger Applications
Rule of thumb: For every 1 million increase in number of records for a monthly application, we need an extra 200 MB of virtual space.
Important Note to Remember: In HFM 32 bit, 3,000,000 is probably the maximum value forMaxNumDataRecordsinRAM that should ever be used provided /3GB switch is also enabled on HFM application server (refer to section “Tune Windows /3GB switch” on how to properly tune /3GB switch performance). That would also result in 450MB of RAM for data caching. In order to set largerMaxNumDataRecordsinRAM i.e. more than 3 million and MaxDataCacheSizeinMB to more than 500 consider HFM 64bit version on Windows 2003 (x64) 64bit OS.
HFM 64 BIT Memory Settings for Larger Applications
