I have noticed (especially when working through a slow line) that vault is not "clever", when it comes to using external "diff" programs on historical versions.
Furthermore, I have to pay for this non-cleverness by waiting .
Scenario: I ask for recursive "diff" of two versions of a folder.
Vault now builds two complete copies of the folder on my computer, and invoke my "diff" program on these folders.
The problem is that all files are transferred from the server. There might be many files in the folder, and perhaps only one of them are changed. Nevertherless all the non-diffing files are transferred twice. Furthermore, several of the files might already have been present in my working folder.
Besides spending time, then transferring the same file twice has another unfortunate consequence: the two files get dfferent timestamps. Most "diff" programs would treat the files much more efficient if the timestamps on the "same" file was the same.
Optimization: Use local instead of repository files
Moderator: SourceGear
-
- Posts: 153
- Joined: Tue Jan 20, 2004 2:28 am
- Location: PDC, Copenhagen Denmark
- Contact:
Optimization: Use local instead of repository files
Thomas Linder Puls
Visual Prolog www.visual-prolog.com
Visual Prolog www.visual-prolog.com