Whenever I try to edit a transaction (usually to change/assign a category), it takes a very long time for the transaction to update, during which time the program is unresponsive. Same is true when I try to change the state of the transaction (usually from nothing to reconciled). Seems that this is prevalent only on one of my accounts, which is an older account with many transactions. I'm guessing that it's taking longer just because that part of the database is bigger. So, is there any way to archive the old transactions, or is there another workaround so that I'm dealing with fewer "active" transactions?

I have the same problem. Which version are you using? Performance improvements were announced in 4.7.2, but I have not installed it yet.
I think even with thousands of transactions, responsiveness should be good. I suspect some checks and cross-checks are done for every action on every transaction, leading to exponential cost. Such behavior can almost always be avoided, but it may take some effort.

I'm using 4.6.6. It's only on the account with tons of transactions, so clearly that's the issue. I'd really like to just archive the transactions beyond say a year ago, which would help immensely I think. I'll give the newest version a shot and see if that helps.

If you could update, the new versions are much faster

Hei Ku wrote:If you could update, the new versions are much faster

Yup, just updated using clay ppa, and 4.7.2 is MUCH better. Thanks!