Stephan Beal <sgb...@googlemail.com> writes: > Checksumming, in this sense, is the generation of the so-called R-card. The > R-card is the 3rd or 4th line of defense against corruption, is _very_ > costly to calculate, and is very possibly overkill.
Considering that I already modified 'mtime-changes' settings, I wonder what repercussion on the safety can have disabled checksumming? > The problem here is how the R-card card is calculated. It has to perform an > md5 against ALL files in the repo (all 5000+ of them) for EVERY commit, no > matter how small the change. To get the md5, it has to extract each full > file from the db, which itself is very memory-hungry and may require > traversing/undeltifying/decompressing an arbitrary number of versions of > each file. It's clear that's very expensive. > We might want to consider a heuristic which automatically disables > repo-cksum once a repo reaches a certain file count. Or disabling it by > default (AFAIK the R-card has never once revealed any corruption which has > slipped through other checks). That sound better/good. ;) In any case I believe you understand that the reason to use Fossil is to enjoy its "Simple, high-reliability, distributed software configuration management" mantra. ;) Sincerely, Gour -- It is far better to discharge one's prescribed duties, even though faultily, than another's duties perfectly. Destruction in the course of performing one's own duty is better than engaging in another's duties, for to follow another's path is dangerous. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
