BSo Will never Die and here Is Why - Developing Essbase Applications - page 126

Table 4.1 Cal c Cache Variables

Va r i a b l e Description

C Lock block value

S Expanded block size

u Estimated number of concurrent users

Figure 4.8 Members in dense dimensions. (From Oracle Essbase Administration Services. With permission.)

The lock block value is displayed in the log if the calc script contains “Set msg
Summary” or “Set msg Detail.” The message looks as follows:

Maximum Number of Lock Blocks: [5000] Blocks

to calculate the expanded block, the total members in the dense dimension are used
instead of stored members, as shown in Figure 4.8. using Sample.Basic as an example,
the expanded block size is 19 * 17 = 323 cells or 2584 bytes (8 bytes per cell).
In this pretend world, 15 simultaneous users are expected; the Dynamic Calc Cache
should be set to 5000 * 2584 * 15 or 193,800,000 bytes. A Dynamic Calc Cache of this
size can hold 75,000 blocks.
going forward, the dynamic calc cache can be monitored using the application log.
As reports are executed, the kernel writes informational messages showing the number
of blocks inserted into the cache.

Extractor Big Blocks Allocs -- Dyn.Calc.Cache:[9504] non-Dyn.Calc.
Cache:[0]

The first half of the message indicates that this report needed 9504 blocks and they
all fit in the cache. If the non-Dyn.Calc.Cache value is consistently greater that zero,
consider raising the size using the DynCALCCAChEmAxSIzE in the Essbase.cfg.