Dynamsoft Forums

We do a get latest at our remote site each night to keep the proxy cache primed and ensure optimal performance for our remote developers.

I notice that on the root SAW server this creates a large number of files and folders in the 'SAW temp' folder, containing what look like reconstructions of the files fetched - they all have names derived from the underlying VSS 'physical' files and versions.

Why is this folder not being deleted immediately? Is there any way to force the temp folder to flush or enforce a maximum size?

SAW is great but it would be really helpful to know what is the best way to squeeze out every drop of performance from the system. Any plans to produce a best practice deployment guide?

Currently, there are two kinds of files that are saved to the temporary folder: the temporary files and cache files. The temporary files are deleted automatically right after they are used. The cache files are stored in the folder until the service is restarted.

The cache mechanism of SourceAnywhere for VSS at the server side improves the performance greatly. We have many customers who have more than 200 developers working on one SourceAnywhere for VSS server and everything is fine.

Currently, there is no such setting to enforce a maximum cache size, since our architect/designer thinks the storage is very cheap and usually a VSS database is only several G big. We have added the feature into our issue tracking system for consideration of a future release. Thanks for your suggestion.


> SAW is great but it would be really helpful to know what is the best way to squeeze out every drop of performance from the system. Any plans to produce a best practice deployment guide?

We do not have a formal document for this, but you can consider the following points:
1. Install SourceAnywhere for VSS server on the same machine where the VSS database is. This can improve the performance greatly;
2. If you have more than 1 hard drivers, use a separate driver for the temp folder of SourceAnywhere for VSS server;
3. If you have any anti-virus software installed on the server, remove the VSS database and the temp folder of SAW for VSS from the protection of the anti-virus software;
4. If you are access SourceAnywhere for VSS server remotely, always enable Compression at the client side;
5. If you have more than 1 developers in one remote location, setup a cache server ,which can improve the performance greatly;
6. There are several other performance-related settings at the server and the client side, but you can just leave them as default.

If you have any other question regarding the performance and other issues, please feel free to contact us. We can schedule a GoToMeeting session with you to review your settings.

Thanks and have a great day.