Thus said Donny Ward on Sat, 21 Jun 2014 17:29:07 -0700:
I have two versions of my repository that I've saved from a while ago,
the last time I ran into this syncing issue. I've linked them both
here, hoping that someone can analyze them and figure out what the
issue is.
Ok, the
Thus said Andy Bradford on 24 Jun 2014 00:21:23 -0600:
If I understand this correctly, it will delete from the unclustered
table but leave behind any newly added cluster artifacts that were
just created. But what about phantoms that might exist in the
unclustered table at that
Thus said Andy Bradford on 24 Jun 2014 00:39:20 -0600:
Perhaps the cluster rotation mechanism is rotating out clusters faster
than clients are able to consume them in this scenario? So clients
that update infrequently will miss some clusters which will exist in
the unclustered table for
Hi
[FYI]
TH1 interpreter (important part of Fossil project) runs almost five
days on Tabletsat-Aurora satellite http://sputnix.ru/en/mediainfo.
The TH1 sources (src/th.[ch] and src/th_lang.c) were used `AS IS' from
Fossil project. Many TH1 commands were implemented to test, manage, and
glue
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm having trouble with each commit taking about 45 seconds in a new
repository I initially populated with 5154 files totaling 425
megabytes. At this point, there are only five or six commits.
I understand Fossil's SHA1 code has been found to be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/24/2014 3:12 PM, Andy Goth wrote:
I'm having trouble with each commit taking about 45 seconds in a
new repository I initially populated with 5154 files totaling 425
megabytes. At this point, there are only five or six commits.
I
On 6/24/2014 14:12, Andy Goth wrote:
I'm having trouble with each commit taking about 45 seconds in a new
repository I initially populated with 5154 files totaling 425
megabytes. At this point, there are only five or six commits.
Does this happen when committing a new file to the repo, or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/24/2014 3:22 PM, Warren Young wrote:
On 6/24/2014 14:12, Andy Goth wrote:
I'm having trouble with each commit taking about 45 seconds in a
new repository I initially populated with 5154 files totaling
425 megabytes. At this point, there
On Tue, Jun 24, 2014 at 4:12 PM, Andy Goth andrew.m.g...@gmail.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm having trouble with each commit taking about 45 seconds in a new
repository I initially populated with 5154 files totaling 425
megabytes. At this point, there are
On 6/24/2014 14:23, Andy Goth wrote:
On 6/24/2014 3:22 PM, Warren Young wrote:
On 6/24/2014 14:12, Andy Goth wrote:
I'm having trouble with each commit taking about 45 seconds in a
new repository
Does this happen when committing a new file to the repo, or only
when changing an existing
On 6/24/2014 14:27, Richard Hipp wrote:
It might be possible to provide an option to disable this checksum step
for large repos.
Is that step redundant if the repo is stored on a filesystem like ZFS
that does data checksumming?
___
fossil-users
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/24/2014 3:27 PM, Richard Hipp wrote:
On Tue, Jun 24, 2014 at 4:12 PM, Andy Goth
andrew.m.g...@gmail.com wrote: Fossil computes an MD5 hash over
all files in the repository as one of the verification steps prior
to commit. See
On Tue, Jun 24, 2014 at 10:33 PM, Andy Goth andrew.m.g...@gmail.com wrote:
On 6/24/2014 3:27 PM, Richard Hipp wrote:
It might be possible to provide an option to disable this checksum
step for large repos.
This command, run at the top level of the source tree:
find -type f | xargs cat |
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/24/2014 3:41 PM, Stephan Beal wrote:
i agree with Richard's suspicion - the R-card calculation is very
costly in terms of system memory, and puts the allocator through
the wringer. There's lots of db looksups, undeltification and
unzipping
Thus said Richard Hipp on Tue, 24 Jun 2014 16:27:08 -0400:
It might be possible to provide an option to disable this checksum
step for large repos.
Would this be different from the repo-cksum setting?
fossil settings repo-cksum
Thanks,
Andy
--
TAI64 timestamp: 400053a9eb67
On Tue, Jun 24, 2014 at 4:33 PM, Andy Goth andrew.m.g...@gmail.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/24/2014 3:27 PM, Richard Hipp wrote:
On Tue, Jun 24, 2014 at 4:12 PM, Andy Goth
andrew.m.g...@gmail.com wrote: Fossil computes an MD5 hash over
all files in the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/24/2014 4:33 PM, Richard Hipp wrote:
Can you compile fossil with -pg, run a commit, and then consult
gprof to see where it is spending all its time?
I just did an empty commit. It took fifty seconds. Due to machine
availability, I'm using a
On Tue, Jun 24, 2014 at 11:49 PM, Andy Goth andrew.m.g...@gmail.com wrote:
gprof says 89.2% (10.74s) in MD5Transform, 1.16% (0.14s) in MD5Update,
1.08% (0.13s) each in pcache1Fetch and sqlite3VdbeExec. Cumulative
time is shown as 12.04s. I'm not sure where the rest of the time
went, but
Thus said Andy Goth on Tue, 24 Jun 2014 15:12:37 -0500:
I'm having trouble with each commit taking about 45 seconds in a
new repository I initially populated with 5154 files totaling 425
megabytes. At this point, there are only five or six commits.
I generated a repository with
19 matches
Mail list logo
