NVCF and Omniverse Caches#

This section covers cache components for self-hosted NVCF deployments. Caches improve performance by storing frequently accessed content locally, reducing network bandwidth usage and accelerating scene loading.

Overview#

Self-hosted NVCF supports several cache components, grouped by where each is documented.

NVCF Caches#

Container Cache: Accelerates container image pulls by caching NGC images locally.

Omniverse Caches#

Omniverse Derived Cache (OVDC), formerly the Derived Data Cache Service (DDCS): Caches derived content, including compiled shaders, to reduce scene load time and improve rendering performance. This is the recommended shader cache. See Derived Data Caching (OVDC) for the Kit parameters used by derived-data and shader caching.
Omniverse Content Cache (OVCC): Caches USD content from object storage to accelerate scene loading.

Documentation#

Each cache component has documentation covering configuration, deployment, and advanced features.

Configuration#

Cache components are configured using Helm values files. Each cache guide includes:

Base configuration examples
Configuration options and parameters
Performance tuning recommendations
Best practices

Monitoring#

Cache components include Prometheus metrics for monitoring:

Cache hit ratios
Storage utilization
Request throughput
Performance metrics

GXCache (Legacy)#

GXCache, the distributed shader cache used by earlier releases, is deprecated. Starting with 26.10.0, use the Omniverse Derived Cache (OVDC) for shader caching; new deployments should not install GXCache. See Derived Data Caching (OVDC) for the Kit parameters, and add them to your streaming Cloud Function.

Next Steps#

Review cache guides: Read the detailed guides for caches you want to deploy.
Plan your deployment: Determine which caches fit your use case.
Configure caches: Set up Helm values files based on the examples.
Deploy caches: Install caches using Helm or Helmfile.
Monitor performance: Set up monitoring dashboards and alerts.