Your device caches content and ads to prevent the Cortex player and agent from continuously downloading files in real-time. This minimizes bandwidth usage and optimizes player performance. If content and ads are cached locally, the player or agent will retrieve the file from the device. If content and ads are not cached locally, the player or agent will download the file and cache it locally.
The download mechanism that we use to move files is the normal request and response mechanism offered through fetch in JavaScript.
You can view your device's cache in the Internal State view In Fleet. It indicates the path where content and ads are cached on your device. Depending on whether the device is using the player or the agent, the cache section in Internal State shows the following:
- Linux and Windows players—There are separate cache sections for each Cortex application your device is using or has used. For example, if your device is using or has used the Vistar Media Ads app, the cache section shows:
cache::com.vistarmedia.apps.ads. - WebOS players—The cache section shows
lrucache::lite-player. - The agent—The cache section shows
cache.
The following applies to content that was directly added to a strategy through the media library in Cortex Fleet.
| Operating System | Caching behavior |
| Windows Player | 30 days since content was first downloaded |
| Linux Player | 30 days since content was first downloaded |
| webOS Player | 30 days since content was last accessed |
| Windows Agent | 30 days since content was last accessed |
| Linux Agent | 30 days since content was last accessed |
The following refers to ads coming through Vistar's ad server (players that have the Vistar Ads App in their strategy).
| Operating System | Caching behavior | Caching in advance |
| Windows Player* | Default: 30 days since ad was first downloaded | n/a |
| Linux Player* | Default: 30 days since ad was first downloaded | n/a |
| webOS Player | 30 days since ad was last accessed | n/a |
| Windows Agent | 30 days since ad was last accessed | Default: Every hour. This value is configurable. |
| Linux Agent | 30 days since ad was last accessed | Default: Every hour. This value is configurable. |
*Users can adjust the vistar.asset_ttl parameter to change the asset cache duration. The default value is 2592000 seconds.