Learn about the pros and cons of an Amazon S3 file system in comparison to a local file system.
If you upload a file to censhare, censhare generates an asset for the file and saves it in the asset file system. With a local asset file system, censhare first stores the file in the associated temporary asset file system.
Then censhare moves the file to the asset file system. The reason for this is that the censhare Client only has write access privileges for the temporary asset file system but not for the asset file system. Moving the file to on a local storage system is not taken into account. Within Amazon S3 this becomes a time-intensive copy operation. It nearly doubles the amount of time for the entire action.
To minimize latency, censhare avoids this type of copy operation with an Amazon S3 file system. Instead, the Amazon S3 file system serves as both, a temporary asset file system and an asset file system. When the process is finished, the censhare asset management function checks whether the file is already in the asset file system and does not carry out the copy action.
When the check is successful, censhare writes a log entry. The entry contains the following:
The temp file provided to the asset management: s3-assets, file:28/35/283503.tif for asset with id 52956 already is on an asset file system. The file is reused and not moved