Hendrik Boom <[EMAIL PROTECTED]> writes:
> Is there a speed problem, or am I doing something wrong.?
For large numbers of transactions, the current register code doesn't
exactly set speed records. I only have 2000 or so transactions in my
largest accounts, and the speed could be better, even though I'm on a
fast machine. I agree that it's something that needs to be addressed.
I think the bottleneck is in the Gnome Canvas, which is the basis of
the register display. Dave P would know more about that.
> I just imported *all* my Quicken accounts, and then started tracking
> down duplicated entries.
Another topic: what sorts of duplicate transactions are you finding
after QIF import? IIRC you have mentioned two classes of problem: one
is the Opening Balance in non-first-position and one is Quicken
collapsing two splits into one. Are there other types of problem
transactions you have identified?
> My guesses (using psychic debugging, without reference to source code)
> is:
> (a)
> - because gtk+ imposes a scrolling area limit af 32K pixels,
> you have too handle scrollong at a higher level in the protocol.
> - the higher layer is written in guile, which is interpreted (like Java)
> - so scrolling slows down quite a bit.
> (b)
> - deleteing a transaction involves recalculating sizes for the entire
> scroling area, and this also is done in guile, is interpreted, and
> so each deletion might end up taking the same order of magnitude
> of time as some of the analysis activities during importing.
These two are not right. There's no Guile code involved in the
register display at all, that I know of, and certainly not in the
actual display-construction.
> P.S. For what it's worth, my processor is a Pentium running at 39.73
> BogoMIPS; 48 meg of RAM. I'm running SuSE Linux 6.3.
Well, that's hardware that would kindly be called "pathetic" these
days :), but I think gnucash should be able to run fine on it. If it
doesn't, that's something we need to work on.
Bill Gribble
--
Gnucash Developer's List
To unsubscribe send empty email to: [EMAIL PROTECTED]
