On 06/21/2018 05:06 PM, Warren Young wrote:
Are the differences merely at the binary level or is the semantic content also
changing?
Thanks for your reply. The files are not binary. They are C source
files that define large arrays of floating point values. These arrays
are rarely updated, but when they are, most of the values in the array
change.
Try unsetting repo-cksum on this repository, if it’s enabled:
https://fossil-scm.org/index.html/help?cmd=repo-cksum
The total size of the fossil repository file is about 65MB, not a huge
repository. Following your suggestion, I checked the repo-cksum setting
and it was not set. I still tried cloning after running "fossil unset
repo-cksum", "fossil setting repo-cksum 0", and "fossil setting
repo-cksum 1" on the source repository and all cases took about the same
time to complete the clone. That seems to be inline with the
documentation you pointed to, where it it mentions that the setting
applies to checkouts, and there is no mention of cloning.
As mentioned in the original post, the majority of the time taken by the
clone operation seems to be spent re-calculating the delta encoding of
the large table definition files. I do not mind much the time it takes
to commit changes to the large tables, although if that can be improved
it would be welcomed. But once that is done, we have to pay for the
delta encoding on every future clone operation. That is the part I
would like to avoid if possible.
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
