Cache Server做什么
The cache server accelerates the import step. It does not touch source data. The cache server is independent of version control. It is even independent of your current project.
Instead of actually importing an asset Unity will re-use an imported asset another team member or yourself has previously imported and uploaded to the cache server. The Cache Server is completely automatic and happens as part of the import pipeline. How much benefit you get from the cache server depends on the type of assets. Textures and large model files usually take the most time to import thus the speed up will be greatest there. Anything from 2x-100x can be expected!
The first thing Unity does when it is about to import an asset is to generate an MD5 hash of all source data.
For a texture this consists of:
- The source asset: “myTexture.psd” file.
- The meta file: “myTexture.psd.meta” (stores all importer settings).
- The internal version number of the texture importer.
- A hash of all version numbers of all Asset Postprocessors.
Anything that can affect the resulting imported data will be hashed. The Cache Server is a very simple file server that looks up assets by the GUID & Hash of that asset. On the cache server you might have many cached files for the same texture. The cache s