Deciding Whether to Use Cache Memory Locking

Before setting cache sizes, you must enable cache memory locking or leave cache memory locking disabled (the default).

The setting for cache memory locking controls whether the memory used for the index cache, data file cache, and data cache are locked into physical memory, giving the Essbase kernel priority use of system RAM.

To use cache memory locking, you must be using direct I/O (buffered I/O is the default I/O access mode), and direct I/O requires a larger index cache size than buffered I/O. See Managing Database Settings.

Locking improves performance for an Essbase database because the system memory manager need not swap the memory used by the caches when swapping the memory used by Essbase Server. By default, cache memory locking is turned off.

Enabling cache memory locking gives the Essbase Kernel priority use of system RAM. If you enable cache memory locking, leave at least one-third of the system RAM available for non-Essbase Kernel use. If you do not want to give the Essbase Kernel priority usage of system RAM, do not enable cache memory locking.

If you are running Essbase on Solaris, run the Bourne shell script, root.sh, before starting Essbase and enabling cache memory locking. This script sets the server to run in Superuser mode so that it can lock memory. See the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide.

  To enable cache memory locking, use a tool:

Tool

Topic

Location

Administration Services

Enabling Cache Memory Locking

Oracle Essbase Administration Services Online Help

MaxL

alter database enable cache_pinning

Oracle Essbase Technical Reference

ESSCMD

SETDBSTATEITEM 26

Oracle Essbase Technical Reference