[Closed] How shared DDC should be used
Translated question from a licensee:
I'd like to ask about how to use shared DDC.
Suppose that a team is composed of persons who update assets and who don't. In that situation, is it OK to develop while all the members of the team enable shared DDC to be used?
What I am worried about is whether each version of assets could be created separately using the DDC cached data while a number of people have different versions of assets and shared DDC has been enabled to be used.
Also, I would like to know what is the trigger to update DDC? Is there any trigger other than timestamps, such as the file size, the MD5 of the file and the update version within the asset?
For an operational reason, we do not accord the timestamp of Perforce with that of the server but with the date when the local is updated. This is because we want everything to work correctly even if we restore a version to an older one.
In this situation, if having enabled shared DDC to be used and restoring to an old version of asset, the cache will be re-created. So, I would like to know whether getting the cache shared by the server has some impact on other users or not.
The question has been closed May 26 '16 at 06:28 PM by AndrewHurley for the following reason:
The question is answered, right answer was accepted
Everyone should use the same DDC, assuming the file server can handle the load.
This is never a problem. The versioning is quite sophisticated (see below).
It is most like MD5, but it really depends on the asset type. Shaders are based on a SHA256 hash of the source files and many other things. Many assets assign a GUID at import time and use that.
Have confidence that no matter what you do, you will always have the correct data.
We do the same thing. The DDC does not use timestamps for anything.
Everything will work fine. Restoring an old version of the asset will find the old version of the DDC data and this will not interfere with any other version of the asset.
The DDC is stateless and timeless; it works across projects, with any version of any Perforce branch, all at the same time. It was specifically designed to not have the problems that worry you.
answered May 26 '16 at 06:26 PM
Follow this question
Once you sign in you will be able to subscribe for any updates here