KMyMoney is pretty slow to work. It takes around 5 seconds to validate one ne or modified operation from my imported MS Money account. I have no other accounts on KMyMoney. Reproducible: Always Steps to Reproduce: 1. import a MS Money file containing around 5000 lines 2. try to create or modify one operation Actual Results: KMyMoney is pretty slow to work. It takes around 5 seconds to validate one ne or modified operation from my imported MS Money account. I have no other accounts on KMyMoney. Expected Results: I wish it would take less than a second as in MS Money My version is 4.8.5
4.8.5 is probably your Qt version. KMyMoney comes at best as 4.6.3. Is that what you are running?
Here is what I get from Help/about Le 20/07/2013 17:39, Marko Käning a écrit : > https://bugs.kde.org/show_bug.cgi?id=322620 > > Marko Käning <mk-lists@email.de> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |mk-lists@email.de > > --- Comment #1 from Marko Käning <mk-lists@email.de> --- > 4.8.5 is probably your Qt version. > > KMyMoney comes at best as 4.6.3. Is that what you are running? >
Sorry, it's indeed 4.6.3 : Le 20/07/2013 17:39, Marko Käning a écrit : > https://bugs.kde.org/show_bug.cgi?id=322620 > > Marko Käning <mk-lists@email.de> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |mk-lists@email.de > > --- Comment #1 from Marko Käning <mk-lists@email.de> --- > 4.8.5 is probably your Qt version. > > KMyMoney comes at best as 4.6.3. Is that what you are running? >
The low reactivity is general and not only when I create or modify an operation. As soon as I make an action, it takes around 5 seconds to react, hatever the action is. I just imported an account from MS Money with 5000 operations (more than 10 years' history). I'm testing this soft before deciding to adopt it. Le 20/07/2013 17:39, Marko Käning a écrit : > https://bugs.kde.org/show_bug.cgi?id=322620 > > Marko Käning <mk-lists@email.de> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |mk-lists@email.de > > --- Comment #1 from Marko Käning <mk-lists@email.de> --- > 4.8.5 is probably your Qt version. > > KMyMoney comes at best as 4.6.3. Is that what you are running? >
For my perhaps 20 accounts with about 3600 transactions I get this when I run a performance check (start KMM from a cmd window in order to see the console output): --- Starting performance tests --- accountList() First time: 1 msec Total time: 325 msec Average : 0 msec balance(Asset) First time: 0 msec Average : 0 msec totalBalance(Asset) First time: 0 msec Average : 0 msec balance(Expense) First time: 0 msec Average : 0 msec totalBalance(Expense) First time: 0 msec Total time: 769 msec Average : 0 msec transactionList() First time: 7 msec Total time: 679 msec Average : 6 msec transactionList(list) First time: 7 msec Total time: 664 msec Average : 6 msec -------- And if I click into my most active account it takes about 3s until I see the ledger functional. It's much faster on re-entree after this first click (<<1s). What do you get?
See under menu item "Tools" the entry "Performance-Test".
I don't understand how to run a performance check. When I try this option through the Tools menu, nothing happens Le 20/07/2013 19:57, Marko Käning a écrit : > https://bugs.kde.org/show_bug.cgi?id=322620 > > --- Comment #5 from Marko Käning <mk-lists@email.de> --- > For my perhaps 20 accounts with about 3600 transactions I get this when I run a > performance check (start KMM from a cmd window in order to see the console > output): > --- Starting performance tests --- > accountList() > First time: 1 msec > Total time: 325 msec > Average : 0 msec > balance(Asset) > First time: 0 msec > Average : 0 msec > totalBalance(Asset) > First time: 0 msec > Average : 0 msec > balance(Expense) > First time: 0 msec > Average : 0 msec > totalBalance(Expense) > First time: 0 msec > Total time: 769 msec > Average : 0 msec > transactionList() > First time: 7 msec > Total time: 679 msec > Average : 6 msec > transactionList(list) > First time: 7 msec > Total time: 664 msec > Average : 6 msec > -------- > > And if I click into my most active account it takes about 3s until I see the > ledger functional. > It's much faster on re-entree after this first click (<<1s). > > What do you get? >
As I wrote above, start KMyMoney from a command line window and watch its output in that same window when clicking the menu item. This might give the devs a hint.
Are you on the home screen/tab when you are doing the import? If so either try switching to a different screen/tab (Ledger, Payees...) and see if the performance improves. A few months ago I eliminated everything on my home screen except "Assets and Liabilities Summary" because every time I made any change in a ledger it took 10 to 15 seconds to refresh the home screen. Now it only takes 2 or 3 seconds (still too slow but manageable). I'm guessing the same slow update process is required on the home screen every time you import a transaction. I have 8 or 9 years of data in my file with almost 30 active accounts and over 10,000 transactions so I think my file is fairly large. * ---- Brendan* On Sat, Jul 20, 2013 at 11:22 AM, Marko Käning <mk-lists@email.de> wrote: > https://bugs.kde.org/show_bug.cgi?id=322620 > > --- Comment #8 from Marko Käning <mk-lists@email.de> --- > As I wrote above, start KMyMoney from a command line window and watch its > output in that same window when clicking the menu item. > > This might give the devs a hint. > > -- > You are receiving this mail because: > You are the assignee for the bug. > _______________________________________________ > KMyMoney-devel mailing list > KMyMoney-devel@kde.org > https://mail.kde.org/mailman/listinfo/kmymoney-devel >
What do you mean by "start KMyMoney from a command line window" ? Le 20/07/2013 20:22, Marko Käning a écrit : > https://bugs.kde.org/show_bug.cgi?id=322620 > > --- Comment #8 from Marko Käning <mk-lists@email.de> --- > As I wrote above, start KMyMoney from a command line window and watch its > output in that same window when clicking the menu item. > > This might give the devs a hint. >
Open a terminal (konsole or any terminal program) and type kmymoney Hit enter. * ---- Brendan* On Sat, Jul 20, 2013 at 12:28 PM, <noftal@club.fr> wrote: > https://bugs.kde.org/show_bug.cgi?id=322620 > > --- Comment #10 from noftal@club.fr --- > What do you mean by "start KMyMoney from a command line window" ? > Le 20/07/2013 20:22, Marko Käning a écrit : > > https://bugs.kde.org/show_bug.cgi?id=322620 > > > > --- Comment #8 from Marko Käning <mk-lists@email.de> --- > > As I wrote above, start KMyMoney from a command line window and watch its > > output in that same window when clicking the menu item. > > > > This might give the devs a hint. > > > > -- > You are receiving this mail because: > You are the assignee for the bug. > _______________________________________________ > KMyMoney-devel mailing list > KMyMoney-devel@kde.org > https://mail.kde.org/mailman/listinfo/kmymoney-devel >
This command isn't recognized Le 20/07/2013 22:30, Brendan@CoupeWare.com a écrit : > https://bugs.kde.org/show_bug.cgi?id=322620 > > --- Comment #11 from Brendan@CoupeWare.com --- > Open a terminal (konsole or any terminal program) and type > > kmymoney > > Hit enter. > > * > ---- > Brendan* > > > On Sat, Jul 20, 2013 at 12:28 PM, <noftal@club.fr> wrote: > >> https://bugs.kde.org/show_bug.cgi?id=322620 >> >> --- Comment #10 from noftal@club.fr --- >> What do you mean by "start KMyMoney from a command line window" ? >> Le 20/07/2013 20:22, Marko Käning a écrit : >>> https://bugs.kde.org/show_bug.cgi?id=322620 >>> >>> --- Comment #8 from Marko Käning <mk-lists@email.de> --- >>> As I wrote above, start KMyMoney from a command line window and watch its >>> output in that same window when clicking the menu item. >>> >>> This might give the devs a hint. >>> >> -- >> You are receiving this mail because: >> You are the assignee for the bug. >> _______________________________________________ >> KMyMoney-devel mailing list >> KMyMoney-devel@kde.org >> https://mail.kde.org/mailman/listinfo/kmymoney-devel >>
Since this is on Windows you'd have to klick the start button, click the "Run..." button, enter "cmd" in the edit file and hit enter. A command line window will now open. Then you will probably have to run KMyMoney.exe by entering its whole path, e.g. stg like "C:\Program Files\KMyMoney\KMyMoney.exe" and hit enter again. Then KMM is going to start. Now you select the mentioned menu item for the performance test. Also you might see other useful information in that cmd-Window.
Here is the result : Le 20/07/2013 22:36, Marko Käning a écrit : > https://bugs.kde.org/show_bug.cgi?id=322620 > > --- Comment #13 from Marko Käning <mk-lists@email.de> --- > Since this is on Windows you'd have to klick the start button, click the > "Run..." button, enter "cmd" in the edit file and hit enter. > > A command line window will now open. > > Then you will probably have to run KMyMoney.exe by entering its whole path, > e.g. stg like "C:\Program Files\KMyMoney\KMyMoney.exe" and hit enter again. > > Then KMM is going to start. > > Now you select the mentioned menu item for the performance test. > > Also you might see other useful information in that cmd-Window. >
Where is the result?
Please note: if you use email reply to the bug, instead of posting directly to the bug at bugs.kde.org, the entire message gets used as the next comment in the bug. The results in a lot of duplicated stuff. Also, attachments are apparently not accepted to the bug by email - you have to upload an attachment directly.
Created attachment 81230 [details] Result of performance test Here is the result of my performance test
I see now that your results for "transactionList" and "transactionList(list)" are quite large. What kind of computer are you using and which Windows version are you running? I guess that info could help the devs.
I work on a recent Win 7 pro (64 bits) computer which was recently bought : Toshiba R930 Portege intel core i5
Marking as duplicate, because of the same symptoms. *** This bug has been marked as a duplicate of bug 272398 ***