Hello,
I've Fossil repo mostly containing uncompressed Gnucash XML files and
commits even for trivial changes are quite slow:
$ time fossil ci -m update logs
You need a passphrase to unlock the secret key for
user: Gour-Gadadhara Dasa g...@atmarama.net
4096-bit RSA key, ID 52B5C810, created
On Sun, Jul 20, 2014 at 1:52 PM, Gour g...@atmarama.net wrote:
New_Version: 6d606bba0322d91e38a5e36541264ff3e9f0036b
24.30user 0.55system 0:27.02elapsed 91%CPU (0avgtext+0avgdata
40804maxresident)k
0inputs+7304outputs (0major+39916minor)pagefaults 0swaps
...
checkins: 973
files:
Thus said Stephan Beal on Sun, 20 Jul 2014 14:03:12 +0200:
fossil commit -m ... --delta
Excellent! I always wondered how to turn on delta manifests. Does this
turn it on for the entire repo, or just the files in the commit?
Thanks,
Andy
--
TAI64 timestamp: 400053cbde68
On Sun, Jul 20, 2014 at 5:20 PM, Andy Bradford amb-fos...@bradfords.org
wrote:
Thus said Stephan Beal on Sun, 20 Jul 2014 14:03:12 +0200:
fossil commit -m ... --delta
Excellent! I always wondered how to turn on delta manifests. Does this
turn it on for the entire repo, or just the files
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?
then, on the next commit:
fossil commit -m ... --delta
Did that, but not much improvement so far.
Can you try that
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
Stephan Beal sgb...@googlemail.com writes:
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).
Gour wrote:
Stephan Beal sgb...@googlemail.com writes:
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
I've added a new comment printing algorithm on the 'experimental' branch.
By default, it uses the existing algorithm. The --comfmtflags option can
be used to enable the new algorithm.
The goals of the new algorithm are to preserve the existing formatting
already present within the comment
Eric Rubin-Smith eas@gmail.com
writes:
Maybe try this?
fossil setting repo-cksum off
Then re-test.
That had drastic effect:
$ time fossil ci -m update logs
You need a passphrase to unlock the secret key for
user: Gour-Gadadhara Dasa g...@atmarama.net
4096-bit RSA key, ID 52B5C810,
Stephan Beal sgb...@googlemail.com writes:
i don't have any more ideas off-hand, but i've never worked with repos
having anywhere near that many files.
After seeing that Eric's advice to turn checksumming off helps, I wonder
if there is something which can be done to make Fossil operate
11 matches
Mail list logo
