On Tue, May 26, 2015 at 12:57 PM, Richard Hipp <d...@sqlite.org> wrote: > How long does this take: > > fossil commit --dryrun -f -m 'not a real commit' >
Here it is: fossil commit --dry-run -f -m 'not a real commit' 24,79s user 6,26s system 63% cpu 48,602 total > What if you first do: > > fossil setting mtime-changes on > fossil setting repo-cksum off > After the above two settings I've got: fossil commit --dry-run -f -m 'not a real commit' 0,15s user 0,05s system 24% cpu 0,834 total With only cksum off and mtime on: fossil commit --dry-run -f -m 'not a real commit' 3,95s user 0,67s system 87% cpu 5,280 total and the opposite (chksum on and mtime off): fossil commit --dry-run -f -m 'not a real commit' 21,74s user 4,60s system 97% cpu 27,006 total Therefore, as suggested, the double checksum of the repository is slowing down things, and enabling mtime is speeding up a little more. Thanks, Luca _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
