Examining and adjusting MVFS cache size

DevOps Code ClearCase® hosts that use dynamic views might benefit from MVFS cache tuning. Default MVFS cache sizes scale automatically based on host memory and are appropriate for a wide range of client needs, but you might want to change default MVFS cache sizes to improve performance in specific cases after performing a performance evaluation in your environment.

All cache tuning requires an intelligent trade-off between specific performance benefits that might result from larger caches and the potential for degraded application performance due to the dedication of more physical memory to caches. Cache tuning can help reallocate the MVFS's use of available memory in ways that reflect a particular host's patterns of use, but it cannot compensate for inadequate physical memory. Furthermore, there are trade-offs that need to be made in multi-processor (multi-core) systems, where increasing the cache sizes can increase locking overhead and could introduce lock contention. All performance tuning should be done in conjunction with a controlled performance evaluation in your environment.