Overview

../../_images/create_splash-image_small-dragon1.jpg

Introduction

Omniverse Cache is a simple service that can be used both on users’ workstations as well as within infrastructure to optimize data transfers between Nucleus and it’s Clients ( Apps, Connectors, and others).

Omniverse Cache speeds up your users by keeping the data close to them and avoiding the need to download files. This also serves to remove the burden on the server and allow even more users to work much faster.

Further, Omniverse Caches can be chained together to allow for optimal performance for your clients. Remote caches are covered under Chaining Caches below.

Architecture

Note

We recommend reviewing Nucleus Architecture for better understanding of caches.

Omniverse Cache’s idea is really simple: it can store locally, and return, files normally served by Nucleus, as long as they haven’t changed.

../../_images/tmp_cache_principal_diagram.png

A few notes and details:

  • A Cache is something a Client connects to. This means that one Cache installation or instance will cache all requests to every Nucleus made thru it

  • Files served by Workstation installations of Nucleus are not cacheable due to those installations missing Nucleus LFT - the HTTP endpoint for downloading files (Cache relies on HTTP)

  • A Cache can itself be a client of another Cache. In other words, caches can be daisy chained - meaning that one Cache can be set as an upstream for another Cache

Chaining Caches

Caches can be “chained” - meaning that one Cache can use another Cache to access Nucleusii.

../../_images/tmp_cache_daisy_chaining_diagram.png

This allows system administrators to design configurations of caching for their users’ workstation much more sophisticated than just a simple single cache service on those workstations.

For some practical examples of chaining, please examine notes on Caches in Infrastructure.