performance tuning guide - MKS

MKS Integrity Client SI Cache Too Small
When the client cache is too small for current usage, performance degrades and data must be
re-acquired from the server cache at regular intervals.
Check the client log files for warning messages such as the following:
Chicago_IS: Full Cache Cleanup: collected 1000 items; ending size: 1000…
Warning:
Two successive cache collections in less than 60 minutes (15 minutes).
If this happens regularly, you may have to allocate more memory to the
cache.
MKS Source includes a mechanism that prevents thrashing in the client cache when opening
new GUI views and when using the command line interface or scripts. This mechanism prevents
data dropping from the client cache when it is too small to receive the requested information.
The mechanism helps to reduce network traffic and the load on the server/proxy.
The cache governor automatically increases maximum size of a cache to fit the data required for
all opened views. When the MKS Integrity Client is restarted, the cache is automatically restored
to its original size. This feature allows users to occasionally work with more views than they
usually do, without having to update their settings or experience poor performance.
Although the cache is designed to increase to accommodate occasional peaks, it is still
necessary to adjust the individual MKS Integrity Client settings for more demanding
requirements. You should increase the size of the corresponding client cache if you regularly see
messages such as the following:
Cache too small. Current Size=1499500, Current Max Size=15000000, New Max
Size=16000000
Tokyo_Dev: Cleanup Failure: collected 1000 items; ending size: 16000000,
cache grown
When working against multiple servers, it is also important to verify that all of the client caches
are large enough to meet your requirements. Rather than immediately modifying the setting for
a well-tuned client cache, you should first carefully check the log file for the name to
confirm which specific client cache is causing the problem. For example, in the preceding sample
logs, there are problems with the caches for Chicago_IS (two successive cleanups in less than
60 minutes) and Tokyo_Dev (cleanup failure).
To increase the client cache, adjust the property for si.ClientCache..size. For
more information, see “
MKS Integrity 2007—Memory Management and Performance Tuning
37