On Sun, Jul 20, 2014 at 5:58 PM, Gour <g...@atmarama.net> wrote: > Stephan Beal <sgb...@googlemail.com> writes: > > > fossil set mtime-changes 1 > > Strange that it was 'off', although default should be 'on'. If not set, > Fossil checks hashes, right? >
Correct about the hashing, but i don't recall what the default is/should be. i suspect that hashing is the default because it's guaranteed to be correct, whereas mtime checks are a close (and much faster) approximation littered with corner cases. > > then, on the next commit: > > > > fossil commit -m ... --delta > > Did that, but not much improvement so far. > Bummer :(. > > Can you try that out? > > I also tried to disable gpg-signing, but not much influence. It seems > that I need to wait some time or more commits to see how it goes. > i don't have any more ideas off-hand, but i've never worked with repos having anywhere near that many files. Maybe a list-member who has can suggest something. Maybe it's something as simple as changing the sqlite3 write mode (and maybe it's not). Your repo isn't on a network mount, is it? If so, all bets are off - network drives are generally problematic for i/o-heavy apps. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
