It's been rumoured that Per Bojsen said:
>
> As I mentioned in a previous email, I'm currently working on
> converting 3-4 years of Pocket Quicken data to GnuCash format. I have
> about 4000-5000 transactions split over 100+ accounts. I was
> wondering if anybody has any experience with how GnuCash manages with
> this amount of data. I noticed that accounts with 100s of
> transactions are slow to react to date range changes. Slow meaning
> in the order of several seconds on a Pentium 166MHz machine.
gnucash does have a mini query engine built in, but it is hard to imagine
that it would be *that* slow. However, it does use the unix-standard
sort() routine which is known to behave pathologically sometimes.
It possible that this is also a GUI problem.
> What part of the system is most likely to be responsible for the
> processing delay? Is it in the engine or the GUI part?
Well, the thing to do would be to compile & run gprof on it,
and see where the cpu syscles were going ...
> I guess I could work around this buy archiving old data. I like
> having all data available but it makes sense to start over with a
> clean GnuCash file once a year. A script that archives transactions
> older than a certain date would be useful.
>
> Do people normally archive old data rather than keeping it online
> forever?
One normally "closes the books" at the end of every fiscal year.
If minor corrections/changes do need to be made, they are done
as adjustments in the new year, without changing old data.
Gnucash does not currently support and "close the books" feature.
--linas
----- %< -------------------------------------------- >% ------
The GnuCash / X-Accountant Mailing List
To unsubscribe, send mail to [EMAIL PROTECTED] and
put "unsubscribe gnucash-devel [EMAIL PROTECTED]" in the body
