This repository has been archived by the owner on Jan 9, 2023. It is now read-only.
Releases: Unity-Technologies/unity-cache-server
Releases · Unity-Technologies/unity-cache-server
v6.4.0
Improvements
- Added --host CLI argument (Server.host config value) to bind the server to a specific interface (#115)
- Added --diag-client-recorder option, which records all client data to disk for debugging and performance testing purposes
- Consolidated log level 4 & 5; log level 4 is now the highest (debug level)
- Improved error handling on client connection error
- Updated to latest Node.js LTS release (v12.13.1)
Bug Fixes
- Fixed null ref exception (#100)
- Performance and memory optimization for very large projects, when a client sends a download request for 10k files or more (#114)
- Fixed a bug where put transactions rejected by whitelist restrictions were affecting the reliability factor, when High Reliability mode is enabled. This meant that an asset was not cacheable if a non-whitelisted client was the first to try to upload it. (#118)
- Server will wait for command processor to finish before shutting down streams after socket disconnect (#137)
v6.4.0 (BETA 5)
- Update to latest Node LTS release (v12.13.1)
- Improved error handling on client connection when using the Unity project Library Importer
- Improved logging when encountering an ECONNRESET error
v6.4.0 (BETA 4)
- Fixed #137; server will wait for command processor to finish before shutting down streams after socket disconnect
- Improved error handling on client connection error
v6.4.0 (BETA 3)
- Added
--diag-client-recorder
option, which records all client data to disk for debugging and performance testing purposes - Updated to latest Node.js LTS release (v10.16.0)
v6.4.0 (BETA 2)
Install beta via npm: npm install -g unity-cache-server@beta
- Performance and memory optimization for very large projects, when a client sends a download request for 10k files or more (#114)
- Added
--host
CLI argument (Server.host
config value) to bind the server to a specific interface (#115) - Fixed a bug where put transactions rejected by whitelist restrictions were affecting the reliability factor, when High Reliability mode is enabled. This meant that an asset was not cacheable if a non-whitelisted client was the first to try to upload it. (#118)
- Fixed null ref exception (#100)
- Consolidated log level 4 & 5; log level 4 is now the highest (debug level)
- Update Node version dependency to latest LTS release (10.15.3)
v6.3.0
- Upgrade to latest Node LTS release (v10.15.2)
v6.2.5
- Reduced high memory usage in worker processes (#95)
- Fixed a crash in the cleanup script when using the --dry-run option (#98)
- Correctly identify unique clients behind NAT firewalls in high reliability mode (#103)
- Fixed null ref exceptions (#100)
- Improved test coverage for transaction mirroring
- Added client address to connection summary statistics log output (thanks @xykong)
v6.2.4
v6.2.3
- Refactor core file read handling to remove all async loops causing 100% cpu usage in some situations, and to improve readability and error handling.
- Fix crash in cluster messaging (#84)
- Ensure all config values fallback to a default (#86)
- Remove most CLI default values, as they will supersede config file values, which is not the expected behavior.
- Fix CLI help output to not display
(default: null)
for every option - Make CLI help text consistent with documentation