Donald Allen writes:
> Some good news:
>
> Doing this the easy way first, I did a little manual pc sampling. I
> ran gnucash (today's trunk) under gdb, let it get to the point where
> it begins to load my data from postgresql, and periodically ctrl-c'd
> in gdb and copied the interrupted location
On Thu, 2010-02-25 at 09:49 +0100, Christian Stimming wrote:
> Zitat von Phil Longstaff :
> >> http://lists.gnucash.org/pipermail/gnucash-devel/2009-August/026121.html
> >> and
> >> my commit r18675 recently. I didn't apply this to the full source
> >> tree so far
> >> in order not to destroy so
Zitat von Phil Longstaff :
http://lists.gnucash.org/pipermail/gnucash-devel/2009-August/026121.html and
my commit r18675 recently. I didn't apply this to the full source
tree so far
in order not to destroy some people's diffs which are still waiting to be
applied... I think the directory you'r
On Wed, 2010-02-24 at 22:18 +0100, Geert Janssens wrote:
> On Wednesday 24 February 2010, Phil Longstaff wrote:
> > On Wed, 2010-02-24 at 20:50 +0100, Christian Stimming wrote:
> > Christian, could you create such a central file with the options you are
> > using?
> >
> Agreed on the idea of an op
On Wednesday 24 February 2010, Phil Longstaff wrote:
> On Wed, 2010-02-24 at 20:50 +0100, Christian Stimming wrote:
> > > So I applied the same treatment to load_splits_for_tx_list,
> > > substituting g_list_prepend for g_list_append inside the
> > > split-fetching loop and reversing the list on co
On Wed, 2010-02-24 at 20:50 +0100, Christian Stimming wrote:
> > So I applied the same treatment to load_splits_for_tx_list,
> > substituting g_list_prepend for g_list_append inside the
> > split-fetching loop and reversing the list on completion of the loop.
> > I rebuilt and tried again and now m
On Wed, Feb 24, 2010 at 12:09 PM, Jeff Kletsky wrote:
> On 2/24/2010 11:50 AM, Christian Stimming wrote:
>
>> As for the patch and indentation: Indeed we discussed and agreed on some
>> common indentation last summer, and we agreed on using the tool astyle to
>> reformat the code as decided. See
On Wed, 2010-02-24 at 14:37 -0500, Donald Allen wrote:
Great! I'll apply the patch. There are probable other places which
would benefit from this. There might also be places where the order is
unimportant so that the list doesn't need to be reversed.
> BTW, I found the indentation/formatting o
On 2/24/2010 11:50 AM, Christian Stimming wrote:
As for the patch and indentation: Indeed we discussed and agreed on some
common indentation last summer, and we agreed on using the tool astyle to
reformat the code as decided. See
http://lists.gnucash.org/pipermail/gnucash-devel/2009-August/026121
> So I applied the same treatment to load_splits_for_tx_list,
> substituting g_list_prepend for g_list_append inside the
> split-fetching loop and reversing the list on completion of the loop.
> I rebuilt and tried again and now my data loads in about 9 seconds,
> approximately the same as the xml
Some good news:
Doing this the easy way first, I did a little manual pc sampling. I
ran gnucash (today's trunk) under gdb, let it get to the point where
it begins to load my data from postgresql, and periodically ctrl-c'd
in gdb and copied the interrupted location and a backtrace to an emacs
buffe
On Wed, Feb 24, 2010 at 10:32 AM, Phil Longstaff wrote:
> On Wed, 2010-02-24 at 09:59 -0500, Derek Atkins wrote:
>> Donald Allen writes:
>>
>> >> I think true measurements will be the only way to find out what causes
>> >> delays
>> >> where.
>> >
>> > Of course. I spent a big chunk of my career
On Wed, 2010-02-24 at 09:59 -0500, Derek Atkins wrote:
> Donald Allen writes:
>
> >> I think true measurements will be the only way to find out what causes
> >> delays
> >> where.
> >
> > Of course. I spent a big chunk of my career doing performance analysis
> > on various bits of complicated so
Donald Allen writes:
>> I think true measurements will be the only way to find out what causes delays
>> where.
>
> Of course. I spent a big chunk of my career doing performance analysis
> on various bits of complicated software and learned very young (the
> hard way) that if you think you know h
On Tue, Feb 23, 2010 at 11:40 AM, Geert Janssens
wrote:
> On Tuesday 23 February 2010, Donald Allen wrote:
>> On Tue, Feb 23, 2010 at 9:15 AM, Geert Janssens
>> > Your assumptions on how things work are correct.
>> >
>> > And I noticed this performance decrease as well.
>> >
>> > There is one diff
On Tuesday 23 February 2010, Donald Allen wrote:
> On Tue, Feb 23, 2010 at 9:15 AM, Geert Janssens
> > Your assumptions on how things work are correct.
> >
> > And I noticed this performance decrease as well.
> >
> > There is one difference between the xml and the sql backends that may
> > influenc
On Tue, Feb 23, 2010 at 9:15 AM, Geert Janssens
wrote:
> On Tuesday 23 February 2010, Donald Allen wrote:
>> As I've mentioned in other posts, I have a pretty large gnucash
>> datafile -- more than 20 Mb uncompressed. I've been testing the SQL
>> backend and I'm concerned about the performance, pa
On Tuesday 23 February 2010, Donald Allen wrote:
> As I've mentioned in other posts, I have a pretty large gnucash
> datafile -- more than 20 Mb uncompressed. I've been testing the SQL
> backend and I'm concerned about the performance, particularly startup
> performance.
>
> I've been doing this t
As I've mentioned in other posts, I have a pretty large gnucash
datafile -- more than 20 Mb uncompressed. I've been testing the SQL
backend and I'm concerned about the performance, particularly startup
performance.
I've been doing this testing on an inexpensive little HP desktop
machine, dual-core
19 matches
Mail list logo
