Deltafication

If both the current version and previous version of the file are less than a certain size 16MB, the previous version will be considered for "deltafication", which is done by a background job. ❋ Bill Heys (2011)

This deltafication mechanism applies to the database storage layer. ❋ Bill Heys (2011)

However, a user checks-out a file from the target branch (DEV), makes changes, and checks-in a new version of the file into this branch (DEV), a new chain is started and no deltafication happens. ❋ Bill Heys (2011)

The results from deltafication vary greatly depending on what type of file it is, and the nature of the changes. ❋ Bill Heys (2011)

However, with shelvesets, no deltafication happens. ❋ Bill Heys (2011)

Next, if the user once again checks-out this same file from the target branch, makes changes, and checks-in a new version to this branch (DEV), then the previous version of the file in the target branch (DEV) will be considered a candidate for deltafication. ❋ Bill Heys (2011)

Only when the first real change is made in this new branch, is a new deltafication chain is started for changed files. ❋ Bill Heys (2011)

The TFS deltafication diff algorithm makes heavy use of compression, so compressibility of the data makes a big difference. ❋ Bill Heys (2011)

Following the branch operation, a user checks-out a file from the source branch (MAIN), makes changes (edits), and checks-in a new version of this file with these changes, The previous version of this file (which is now used by both the MAIN and DEV branches in this example) will be considered for deltafication. ❋ Bill Heys (2011)