33.3 View Caches

To speed its performance, the view_server process associated with a view maintains a cache. The default size of this cache is 500 KB (1 MB for some 64-bit UNIX platforms). You can configure a larger cache size to boost performance. A larger cache is particularly useful for views in which very large software systems are built by omake or clearmake.

The view_server maintains a number of caches, consisting mostly of data retrieved from the VOB, to respond faster to RPCs from client machines. These are the view caches:

• Object cache, which facilitates retrieval of VOB and view objects (for example, versions and branches)

• Directory cache, which facilitates file system directory read access

• Stat cache, which stores file attributes

• Name cache, which stores names (of existing files and names that do not exist in a directory) and accelerates name lookups

When a view_server process is started, it chooses its cache size from the first one of these that yields a value:

• A persistent value set when the view was created (cleartool mkview -cachesize) or modified with the cleartool setcache -view -cachesize command.

• Contents of the file /var/adm/atria/config/view_cache_size or ccase-home-dir\var\config\view_cache_size (decimal number; set with setcache -view -host)

• Site-wide cache default stored in the ClearCase registry (set with setcache -view -site)

• Default value: 512 KB on 32-bit platforms, 1 MB on 64-bit platforms

The view cache size represents the total number of bytes available for allocation among the individual view caches.

See the setcache reference page for information about setting the cache size for a view and for a site, and the getcache reference page for information about displaying cache information.