Hi, several months ago, I asked a question about the mechanism DVC use to manage large file versioning.
The example given was for a 10 Go file managed by DVC, a new version of the file is committed with a very small change. What will be the storage impact on this commit?
The answer I got was that the storage usage will be doubled, so 20 Go used after the new version’s commit. Because DVC doesn’t compare changes inside a large file.
I understand there was a plan for DVC to manage changes in large file. So that in my example, instead of double the storage usage, only the changed part will be stored on top of the base version.
My questions are :
- Is there a timeline to implement this new feature?
- Does DVC compare file content while versioning small files?