I'm a new user just trying to transfer my accounts to KMM 4.6.3 from Moneydance. KMM is very impressive, except for the fact that it is excruciatingly slow. In my accounts w/ larger numbers of transactions (e.g. checking) it takes several seconds for pretty much every action, including just accepting a downloaded transaction. Switching to the ledger takes 7-8 seconds in accounts that Moneydance switches to virtually instantaneously. Is this normal behavior? Is there anything I can do to speed it up? I really really really want to like KMM but the poor performance looks like it is a deal breaker unless there is something I can do to improve it.
thanks
PS I'm using KMM 4.6.3 in linux mint 13/kde (4.8.5) on a machine w/ an amd athlon II X4 640.

Are you using the file format or the SQL backend?

I am using the .kmy file format.

You could filter the transactions to only show the latest year or so. Go to Settings > General > Filter

What's the size of the .kmy file?
What's your KDE version?

Thanks very much for the responses and suggestion. I am running KDE 4.8.5 that is installed w/ Linux Mint 13 KDE edition. I also have tried KMM on a gnome machine (LM w/ cinnamon 1.6) w/ similar results. The file is ~944KB, and I believe in total there are about 18K transactions spread over ~20-25 accounts, with checking, saving, credit cards, and various retirement and investment accounts. I don't know if this total includes "closed" accounts. As I mentioned, Moneydance handles this amount of data pretty easily in terms of performance (altho for other reasons I would prefer KMM). I guess I could filter transactions to try and speed things up but I'm leery of just starting out and already resorting to workarounds to deal w/ what seems to me a pretty reasonable amount of data. If the performance I'm seeing is what I should expect, I will no doubt have to stick w/ MD, for all its flaws.

As Hei_Ku mentioned, using the start date filter should improve performance in the current version in your setup. You have collected a lot of transactions and the limitation is due to the code that currently does the display of the ledger. Using said filter limits the number of transactions to be shown in the ledger view. They are still used and available for reports etc. And in case you need to access them in the ledger, turn off the filter.
The limitation is a known bug, but the developers currently have limited time to deal with it (a lot of code needs to be touched). This is still a leftover from the KDE3 to KDE4 port.

OK, thanks for the info. I'm glad to hear this isn't "normal". I can most likely live w/ some workarounds if I can see some light at the end of the tunnel (however faint). Besides this issue, I really like KMM.

I am still using 1.0.5 because of performance. I know 4.6 has improved, but operations in accounts are instantaneous for me with 1.0.5. My kmy file is almost 700 KB and my checking account has some 5,400 references. Maybe worth a try?

Zebulon, thanks for the suggestion. I will look into 1.0.5. I would assume a lot of other things have changed between those versions?

Lots of changes since that version, which is frozen and unmaintained at the moment. It's over 2 years since the last release of the last KDE3 version of KMyMoney.
I wouldn't recommend it.