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 wit
On Tue, Jun 24, 2014 at 11:49 PM, Andy Goth 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 gprof isn't seeing it.
-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 4:33 PM, Andy Goth 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
> > wrote: Fossil computes an MD5 hash over
> > all files in the repository as one of the verification
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
-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
On Tue, Jun 24, 2014 at 10:33 PM, Andy Goth 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 | md5sum
>
> com
-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
> wrote: Fossil computes an MD5 hash over
> all files in the repository as one of the verification steps prior
> to commit. See
> http://fossil-scm.org/index.html
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 mai
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 file
On Tue, Jun 24, 2014 at 4:12 PM, Andy Goth 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 only five or six comm
-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,
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 onl
-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 under
-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 slow
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 s
Thus said "Andy Bradford" on 24 Jun 2014 00:21:23 -0600:
> http://www.fossil-scm.org/index.html/info/41b29f38fdb4e5ed9e0313648160aca055c4eca0
I believe this needs to also look at the shun table. They should
probably be removed from the unclustered table.
Andy
--
TAI64 timestamp: 400
17 matches
Mail list logo
