Unity CacheServer optimized for multi-client local networks
The Unity Cache Server, optimized for locally networked team environments.
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.
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
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:
bash npm install [email protected] -g
npm install github:Unity-Technologies/unity-cache-server -g
Note: GitHub source install from
masterbranch 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
Option | Description -------------------------------- | -----------
--version| Show the version number of the Cache Server.
--host| The interface on which the Cache Server listens. The default is to listen on all interfaces.
--port| The port on which the Cache Server listens. The default value is 8126.
--cache-module [path]| The path to cache module. The Default path is 'cache_fs'.
--cache-path [path]| The path of the cache directory.
--log-level| The level of log verbosity. Valid values are 0 (silent) through 4 (debug). The default is 3 (info).
--workers| The number of worker threads to spawn. The default is 0.
--diag-client-recorder| Record incoming client network stream to disk.
--mirror| Mirror transactions to another cache server. Repeat this option for multiple mirrors.
--putwhitelist| Only allow PUT transactions (uploads) from the specified client address. Repeat this option for multiple addresses.
--dump-config| Write the active configuration to the console.
--save-config [path]| Write the active configuration to the specified file and exit. Defaults to
--help| Show usage information.
config/default.ymlfile 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.
|Global.logLevel||3||Logging level; override with the --log-level CLI command|
|Cache.options.processor.putWhitelist||||Only allow PUT transactions (uploads) from the specified array of IP addresses (string values)|
|Cache.options.workers||1||Number of worker threads; override with the --worker CLI command|
|Server.host||0.0.0.0||The interface on which the Cache Server listens. Override with the --host CLI command|
|Server.port||8126||The port on which the Cache Server listens. Override with the --port CLI command|
|Server.options.allowIPv6||false||Listen for client connections on both IPv4 and IPv6|
You can have multiple configuration files based on environment:
unity-cache-server --save-config config/local-development.yml
To use a custom configuration directory:
unity-cache-server --save-config myCustomConfig/default.yml3)
To dump the current config to the console, run the following command:
The Cache Server section of the Unity Manual contains detailed information on connecting clients to remote Cache Servers.
Cache Server supports two caching mechanisms:
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
A simple, efficient file system backed cache.
|The path to the cache directory.|
|ASP.NET or ISO 8601 style timespan. Cache files that have not been accessed within this timespan are eligible for cleanup. For more information on duration syntax, see the moment library documentation.|
|cleanupOptions.maxCacheSize||0||The maximum size, in bytes, of the cache on disk. To bring the total disk utilization under this threshold, the cleanup script considers files for removal in least recently used order. Set the value to zero (0) to disable the cleanup feature.|
expireTimeSpanoption is used to determine which files to delete. If
maxCacheSizeis 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.
|pageSize||100000000||The page size, in bytes, used to grow the cache.|
|maxPageCount||10||The maximum number of pages to allocate in the cache. The combination of
maxPageCountlimits the overall memory footprint of the cache. When this threshold is reached, memory is recovered using a Least Recently Used (LRU) algorithm.
|minFreeBlockSize||1024||The size of the minimum allocation unit, in bytes, within a page. You can specify a lower value for smaller projects.|
|The path to the cache directory. Dirty memory pages are saved to disk periodically in this directory, and loaded at startup.|
|persistence||true||Enable saving and loading of page files to disk. If
false, the cache is emptied during restart.
|persistenceOptions.autosave||true||When set to
true, automatically save changed memory pages; set to
falseto disable. If
false, pages are only saved when the cache server is stopped with the
qconsole command or with upon a SIGTERM.
|persistenceOptions.autosaveInterval||10000||The frequency, in milliseconds, to save pages that have changed.|
Due to performance considerations, the
cache_fsmodule 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.
node cleanup.js [options]
|-V, --version||Show the version number of cleanup script.|
|-c --cache-module [path]||The path to the cache module.|
|-P, --cache-path [path]||The path of the cache directory.|
|-l, --log-level||The level of log verbosity. Valid values are 0 (silent) through 4 (debug)|
|-e, --expire-time-span||Override the configured file expiration timespan. Both ASP.NET style time spans (days.minutes:hours:seconds, for example '15.23:59:59') and ISO 8601 time spans (For example, 'P15DT23H59M59S') are supported.|
|-s, --max-cache-size||Override the configured maximum cache size. Files will be removed from the cache until the max cache size is satisfied, using a Least Recently Used search. A value of 0 disables this check.|
|-d, --delete||Delete cached files that match the configured criteria. Without this, the default behavior is to dry-run which will print diagnostic information only.|
|-D, --daemon||Daemon mode. Execute the cleanup script at the given interval in seconds as a foreground process.|
|-h, --help||Show usage information.|
--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
--mirroroption cautiously. There are checks in place to prevent self-mirroring, but it is still possible to create infinite transaction loops.
|queueProcessDelay||2000||The period, in milliseconds, to delay the start of processing the queue, from when the first transaction is added to an empty queue. Each transaction from a client is queued after completion. It's a good idea to keep this value at or above the default value to avoid possible I/O race conditions with recently completed transactions.|
|connectionIdleTimeout||10000||The period, in milliseconds, to keep connections to remote mirror hosts alive, after processing a queue of transactions. Queue processing is bursty. To minimize the overhead of connection setup and teardown, calibrate this value for your environment.|
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 (
highReliabilityis 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
multiClientto true forces more than one client to commit the same transaction to increment the counter. Setting
reliabilityThresholdto a value of 0 or 1 disables the reliability checks, but still prevents versions from changing. For debugging purposes, setting
saveUnreliableVersionArtifactsto true isolates and saves all uploads of unstable Asset versions for later inspection and diffing.
|highReliability||false||Enable high reliability mode.|
|highReliabilityOptions.reliabilityThreshold||2||Number of binary-stable imports of the same version required before a version is cached and served.|
|highReliabilityOptions.saveUnreliableVersionArtifacts||true||After a version is declared unreliable, save all subsequent transactions for the version for later inspection and debugging.|
|highReliabilityOptions.multiClient||false||Require multiple clients to upload the same binary-stable version to increment the stability factor. For example, if the same client uploads the same version twice in a row, it does not increase stability of the version.|
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
-executeMethodoption. For the , use
pathis the full path and filename to export. For more information on running the Editor in silent mode and the
-executeMethodoption, see Command line arguments. 3) Run the import utility to begin the import process:
Starting up the Cache Server with the
--diag-client-recorderoption will write to disk raw data from all incoming client connections (by default to the
diagnostics/client-recordingsfolder). Example tools and libraries for analysing recorded sessions can be found in the ucs-diag-tools repository.
|Diagnostics.clientRecorder||false||Enable client network stream recording.|
|Diagnostics.clientRecorderOptions.bufferSize||10000000||Size of in-memory buffer for client network stream recording.|
|Diagnostics.clientRecorderOptions.saveDir||"diagnostics/client-recordings"||Directory where client network stream recordings will be saved. A relative directory will be relative to the server application startup directory.|
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