The Unity Cache Server, optimized for locally networked team environments.

Note: This version of the cache server does not support the new Asset Database Version 2 introduced in Unity 2019.3. For projects using the new Asset import pipeline, use the Accelerator

This repository contains an open-source implementation of the Cache Server. This stand-alone version of Cache Server is specifically optimized for LAN connected teams. The Cache Server speeds up initial import of project data, as well as platform switching within a project.

This open-source repository is maintained separately from the Cache Server available on the Unity website and the implementation of the Cache Server that is packaged with the Unity installer.

• Server Setup
  • Install from npm registry
  • Install from GitHub source
• Usage
• Configuration files
• General Options
• Client Configuration
• Cache Modules
  • cache_fs (default)
  • cache_ram
• Cache Cleanup
• Mirroring
• High Reliability Mode
  • Background
  • Function
  • Configuration
• Unity project Library Importer
• Diagnostics
• Contributors
• License

Download and install LTS version 12.13.x of Node.js from the Node.JS website.

npm install unity-cache-server -g

For the latest beta release:

npm install unity-cache-server@beta -g

npm install github:Unity-Technologies/unity-cache-server -g

Note: GitHub source install from master branch might be ahead of latest release version.

Default options are suitable for quickly starting a cache server, with a default cache location of .cache_fs

unity-cache-server [arguments]

The config/default.yml file contains configuration values for the cache modules (see below) and other features. The config system is based on the node-config module. For additional information on how to manage environment specific config files, see the Configuration Files documentation on the node-config GitHub repository.

You can have multiple configuration files based on environment:

1. export NODE_ENV=development
2. unity-cache-server --save-config config/local-development.yml

To use a custom configuration directory:

1. mkdir myCustomConfig
2. unity-cache-server --save-config myCustomConfig/default.yml
3. export NODE_CONFIG_DIR=myCustomConfig
4. unity-cache-server

To dump the current config to the console, run the following command:

unity-cache-server --dump-config

The Cache Server section of the Unity Manual contains detailed information on connecting clients to remote Cache Servers.

Cache Server supports two caching mechanisms:

• A file system based cache.
• A fully memory (RAM) backed cache.

The file system module is the default and suitable for most applications. The RAM cache module provides optimal performance but requires a sufficient amount of physical RAM in the server system. Typically, this is two to three times size of your Project's Library folder on disk.

Configuration options for all modules are set in the config/default.yml file.

A simple, efficient file system backed cache.

--cache-module cache_fs

• cache_fs is backwards compatible with v5.x Cache Server directories.
• Supports worker threads using the --workers option.
• When you run the cleanup script, the value of the expireTimeSpan option is used to determine which files to delete. If maxCacheSize is specified the script checks whether the cache exceeds the value of maxCacheSize. If it does, the script deletes files in least-recently-used order until the cache no longer exceed maxCacheSize.

A high performance, fully in-memory LRU cache.

--cache-module cache_ram

• Does not support worker threads.

Due to performance considerations, the cache_fs module shipped with Cache Server v6.0 does NOT operate as an LRU cache and does not enforce overall cache size restrictions. This is a change from previous versions of Cache Server. To manage disk usage, a separate cleanup script is provided that can either be run periodically or in "daemon" mode to automatically run at a given time interval.

unity-cache-server-cleanup [option] or node cleanup.js [options]

• Only the cache_fs module supports cache cleanup (cache_ram does not).

Use the --mirror [host:port] option to relay all upload transactions to one or more Cache Server hosts (repeat the option for each host).

Important: Use the --mirror option cautiously. There are checks in place to prevent self-mirroring, but it is still possible to create infinite transaction loops.

High Reliability Mode imposes stricter requirements on upload transactions to increase the integrity of cached data.

Asset versions are cached based on the Asset GUID and Asset hash reported by the client (Unity Editor). The Asset hash is calculated from the inputs to the Asset import process. The import process should produce the same binary result for a given set of inputs, but there is no guarantee that it will. Instability in the import process is typically an indication of a bug or design problem in the Asset importer.These errors can be propagated to other clients because Unity is not able to detect these instabilities before committing them to the Cache Server.

In the default operating mode (highReliability is false), the Cache Server accepts all transactions for all versions of an Asset from any Unity client. In this scenario, the version of an Asset can change after it is already committed and the commit can cause an incorrect or unstable import.

High Reliability Mode allows the Cache Server to compare multiple transactions for the same version for binary stability before committing a version to the cache, and disallows further modifications to already committed versions. When an instability is detected, warning messages are logged and caching of the Asset is suspended until a team member uploads a new version of the Asset.

Requiring multiple imports of the same Asset to ensure the stability of each Asset version is resource intensive. High Reliability Mode is primarily beneficial to developers in networked team environments, where the increased overhead of importing Assets multiple times is distributed across the entire team. The larger the team, the smaller the impact on any individual.

When highReliability is true, a counter for an Asset version is incremented with each transaction that is binary identical to the previous. When the counter reaches the configured reliabilityThreshold, the version is committed to the cache and served. For networked team environments, setting multiClient to true forces more than one client to commit the same transaction to increment the counter. Setting reliabilityThreshold to a value of 0 or 1 disables the reliability checks, but still prevents versions from changing. For debugging purposes, setting saveUnreliableVersionArtifacts to true isolates and saves all uploads of unstable Asset versions for later inspection and diffing.

Tools are provided to quickly seed a Cache Server from a fully imported Unity project (a project with a Library folder).

1. Add the CacheServerTransactionImporter.cs script to the Unity project to export.
2. To save an export data file in .json format, in the Unity Editor, select Cache Server Utilities > Export Transactions . Alternatively, with the script added to your project, you can run Unity in batch mode using the -executeMethod option. For the <ClassName.MethodName>, use CacheServerTransactionExporter.ExportTransactions([path]) where path is the full path and filename to export. For more information on running the Editor in silent mode and the -executeMethod option, see Command line arguments.
3. Run the import utility to begin the import process: unity-cache-server-import <path to json file> [server:port]

• On very large projects, Unity might appear to freeze while generating the exported JSON data.
• The default server:port is localhost:8126
• The import process connects and uploads to the target host like any other Unity client, so it should be safe in a production environment.
• Files are skipped if any changes were detected between when the JSON data was exported and when the importer tool is executed.

Starting up the Cache Server with the --diag-client-recorder option will write to disk raw data from all incoming client connections (by default to the diagnostics/client-recordings folder). Example tools and libraries for analysing recorded sessions can be found in the ucs-diag-tools repository.

Contributions are welcome! Before submitting pull requests please note the Submission of Contributions section of the Apache 2.0 license.

The server protocol is described in protocol.md

Apache-2.0 © Unity Technologies