SQL Woes under 1.6

[Linas Vepstas]

On Sun, Jul 22, 2001 at 10:30:02PM -0400, Michael T. Garrison Stuber was heard to remark:
> The SQL backend for GNUCash is driving me batty.  I'm running GNUCash 1.6.1 
> against PostgresSQL 7.0.3.  I continue to face two problems:
> 
> 1).  The SQL Backend consistently losses my settings for getting stock 
> quotes.  It appears that the setting for this is stored via the KVPFrame as 
> a string setting with the key "old-price-source".  Is this correct?  Is 
> anyone else having these problems?  What did you do to work around them?

Hmm. Well, the sql backend is supposed to handle KVP frames. Did you discover
the name of this kvp frame by reading the source code, or by seeing it in the 
db?  Is it being stored in the db, but just not being fetched correctly? 

> 2).  The performance is abysmal.  Any suggestions on what I can tune, or 
> why it might be so awful?  I've got a PIII-733 w/ 384MB of RAM.  You'd 
> think it would do the job okay.

There was a major performance performance fix in 1.6.1, you're sure you are 
running 1.6.1? 

I presume that the response time is bad for just one particular operation, 
(e.g. opening a register window or running a report) and  not overall? 
If so, then could you run gnucash --loglevel 4 and mail me the output
immediately leading up to the point where it hangs? 

Could you also mention what it is about your dataset that you think is 
unique?  Do you have thousands of accounts?  Maybe one account with 
thousands of transactions in it?

Another time-killer might be that you set up your 'home window' to have 
a dozen reports in it, with each report showing several years worth of 
data in it ... then probably no one operation is slow, but the startup 
time is pitiful ...


--linas


> 
> --
> Michael T. Garrison Stuber
> 
> _______________________________________________
> gnucash-user mailing list
> gnucash-user@lists.gnumatic.com
> http://www.gnumatic.com/cgi-bin/mailman/listinfo/gnucash-user

-- 
I'm very PUBLIC-MINDED, I'm helping a NIGERIAN get his $25,000,000 back!