You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Switching to the buzhash chunker gives a large advantage if files are modified and data is moved around – like in VM images or tar archives. It also works pretty good on zstd archives when using --rsyncable.
As the data which is moved around can still be matched, a deduplication of different versions is possible.
As that's a prime target for using Git LFS, I think it's worth changing the default here to buzhash.
There are no disadvantages, except a bit CPU time spend on doing the rolling hash.
The text was updated successfully, but these errors were encountered:
Currently, the fixed 256 kb chunker is hard-coded.
Switching to the buzhash chunker gives a large advantage if files are modified and data is moved around – like in VM images or tar archives. It also works pretty good on zstd archives when using
--rsyncable
.As the data which is moved around can still be matched, a deduplication of different versions is possible.
As that's a prime target for using Git LFS, I think it's worth changing the default here to buzhash.
There are no disadvantages, except a bit CPU time spend on doing the rolling hash.
The text was updated successfully, but these errors were encountered: