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

Figure 4.5 Sample.Basic index size. (From Oracle Essbase Administration Services. With permission.)
Figure 4.6 Sample.Basic cache statistics. (From Oracle Essbase Administration Services. With permission.)
notice that the current index cache value is now twice as large as the physical
index size. BSo will claim whatever is specified up to the limit of 4,294,967,295 bytes.
If mEmSCALIng is specified in the configuration file, the limit is extended for 64 bit.
Periodically review the index cache size and update the cache accordingly.
4.6.2 Data Cache
Before discussing the data cache, it is important to understand compression and how
it relates to the cache. Physical data blocks are stored in the ESS*. PAg file(s) in com-
pressed form assuming that some lunatic has not turned off compression. There are
three types of compression in BSo: bitmap, rLE, and zLib. zLib is primarily a zipped
format that is slow relative to the other two. zLib is used when disk space is an issue.
Bitmap, as the name implies, places a bitmap in the header of each block. The bitmap
is used to tell BSo which cells have data and which have missing values. As the block
size increases, so does the bitmap size increasing the block header overhead. rLE stands