Some good news...
I came in to work, disabled repo-cksum, on the copy of the repository at
work and tested again. Single file commit took 6 seconds. I made a
number of changes to files (11 files total, a collection of edits, adds
and removes) and did a fossil commit (without specifying files on the
command line) and the commit took about 7 seconds.
There seems to be a minimum time of 6 seconds for my operations of
status, changes, and commit, and it would make sense that they all have
to do the same work at some point (that would be 'finding out what files
have changed')
I don't expect any filesystem level caching going on this time. So, what
happened on my machine at home with the 59 second and 18 second commits
versus the consistent 6-8 second commits at work? At home, my hard
drives are full-disk encrypted via Truecrypt :) There is a behind the
scenes slow-down for all reads and writes. Fossil is not at fault for
that by any means.
In any case... *** disable repo-cksum if you have a large repository ***
I don't know if that "6 seconds" can be improved on, but I am definitely
much happier than I was yesterday.
Thanks everyone for help and insight.
Jeff
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
