[skrooge] [Bug 382152] Skrooge over network data maxes CPU on one core during several seconds when setting an operation's category
https://bugs.kde.org/show_bug.cgi?id=382152 --- Comment #21 from Benoît Robin <benoit.ro...@hoshikaze.net> --- Hi Stéphane, I confirm 2.9.0, which is already installed onmy desktop machine, doesn't have the issue anymore. I'll install it on the laptop. Merci de ton aide ^-^ Btw, who can close the case ? -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 382152] Skrooge over network data maxes CPU on one core during several seconds when setting an operation's category
https://bugs.kde.org/show_bug.cgi?id=382152 --- Comment #19 from Benoît Robin <benoit.ro...@hoshikaze.net> --- Ah, and I'll keep 2.8.1 on the laptop until you tell me you don't need further information... -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 382152] Skrooge over network data maxes CPU on one core during several seconds when setting an operation's category
https://bugs.kde.org/show_bug.cgi?id=382152 --- Comment #18 from Benoît Robin <benoit.ro...@hoshikaze.net> --- Created attachment 107245 --> https://bugs.kde.org/attachment.cgi?id=107245=edit Report of Profiling + SQL Hi Stéphane, I doubled up with the previous trace and the file, which is copied from the console, contains both trace and SQL. This is probably redundant. >From your diagnostic, I guess the statement that causes the issue is the following : ##executeSqliteOrder:SELECT EXISTS(SELECT 1 FROM payee WHERE EXISTS (SELECT 1 FROM payee p2 WHERE p2.id<>payee.id AND upper(p2.t_name)=upper(payee.t_name) AND p2.t_name<>payee.t_name)) TIME=27582 ms, (with fetch):27582 ms It was executed twice, which matches with my observing two CPU max-outs, one at startup and one when I updated the operation's category. Hope that could help you improve that operation. It seems a quite simple brute-force statement on all the base and I'm not SQL-wise enough to know if such a seemingly simple request can be improved ^-^ Benoît 'Mutos' Robin -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 382152] Skrooge over network data maxes CPU on one core during several seconds when setting an operation's category
https://bugs.kde.org/show_bug.cgi?id=382152 --- Comment #17 from Benoît Robin <benoit.ro...@hoshikaze.net> --- Hi Stéphane, And yes, I am French ^-^ As for the test, as the update to 2.9.0 passed on my main computer, I now just can't get the bug anymore. I tried to refresh the advices widget, even turned on all advices, but to no avail. Oh, and as for payees, in French it should be what is called a "tiers", if I understand well. I never bothered to look at those, they're not even displayed in my custom operation format. I'll try on another computer, which didn't get the update, and I give you what I found. -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 382152] Skrooge over network data maxes CPU on one core during several seconds when setting an operation's category
https://bugs.kde.org/show_bug.cgi?id=382152 --- Comment #16 from Benoît Robin <benoit.ro...@hoshikaze.net> --- Hi Stephane, Thanks for the fix and advice ! This morning, I remarked a skrooge update passed and thought you might have found the issue ^-^ I don't know what is a payee, so I can't answer your question about their number. I'll search that. Accounting for me is just importing my bank's files, marking operations with categories and from time to time issuing a report of category summaries. But indeed I have a dashboard with the "advices" widget. I don't need that widget anyway, but it was there, so I kept it. I'll remove it and that's all... Anyway, I'll run the same scenario with the up-trace and we'll see what comes out of it... -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 382152] Skrooge over network data maxes CPU on one core during several seconds when setting an operation's category
https://bugs.kde.org/show_bug.cgi?id=382152 --- Comment #12 from Benoît Robin <benoit.ro...@hoshikaze.net> --- Hi Stephane, hi Christoph, Just attached the profiling information. Hope it'll help you to do Skuld job on the bug ^-^ Best regards, Benoît 'Mutos' Robin -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 382152] Skrooge over network data maxes CPU on one core during several seconds when setting an operation's category
https://bugs.kde.org/show_bug.cgi?id=382152 --- Comment #11 from Benoît Robin <benoit.ro...@hoshikaze.net> --- Created attachment 107224 --> https://bugs.kde.org/attachment.cgi?id=107224=edit Profiling when the issue occurs Scenario : - Console : export SKGTRACEPERFO=1, - Launch Skrooge, - Open my accounting file : shows around 35s of CPU max, - Go to any account, - Tools > Restart Profiling, - Change the category on an operation : shows around 35s of CPU max, - Tools > Open Profiling, - Copy and Paste in 2017-08-12-Profiling-Report.csv file. -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 382152] Skrooge over network data maxes CPU on one core during several seconds when setting an operation's category
https://bugs.kde.org/show_bug.cgi?id=382152 --- Comment #10 from Benoît Robin <benoit.ro...@hoshikaze.net> --- Hi Stephane, just read your comments, I'll run the test when I got time, tomorrow evening at best or by next week-end at worst. -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 382152] Skrooge over network data maxes CPU on one core during several seconds when setting an operation's category
https://bugs.kde.org/show_bug.cgi?id=382152 --- Comment #4 from Benoît Robin <benoit.ro...@hoshikaze.net> --- Copied the file to a local disk and tested. Just the same CPU surge as before, so my conclusion is now that NETWORK IS NOT GUILTY ! Seems my first observation of a second-long surge was wrong... It's a memory from 3 weeks ago, so don't take it into account... Unfortunately, I now have no box left on the old Skrooge version to check with my save of the old file before migration. Btw, I found the old version number : it was 1.9.3 ! -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 382152] Skrooge over network data maxes CPU on one core during several seconds when setting an operation's category
https://bugs.kde.org/show_bug.cgi?id=382152 --- Comment #3 from Benoît Robin <benoit.ro...@hoshikaze.net> --- Removing history reduces file size to 3.5 MB, but doesn't change anything to the CPU surge. I also remarked that, when opening the file, there was a brief (5s) network peak, corresponding to the file read, then the CPU climbed to one core 100% and stayed there for the usual 30-some seconds. Still no network activity during CPU surge. -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 382152] Skrooge over network data maxes CPU on one core during several seconds when setting an operation's category
https://bugs.kde.org/show_bug.cgi?id=382152 --- Comment #2 from Benoît Robin <benoit.ro...@hoshikaze.net> --- Also remarked there is no network activity at all during the CPU surge. -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 382152] Skrooge over network data maxes CPU on one core during several seconds when setting an operation's category
https://bugs.kde.org/show_bug.cgi?id=382152 --- Comment #1 from Benoît Robin <benoit.ro...@hoshikaze.net> --- Seemingly regardless of the number of operations to catgorize, CPU surge is between 25-35s. -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 382152] New: Skrooge over network data maxes CPU on one core during several seconds when setting an operation's category
https://bugs.kde.org/show_bug.cgi?id=382152 Bug ID: 382152 Summary: Skrooge over network data maxes CPU on one core during several seconds when setting an operation's category Product: skrooge Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: guillaume.deb...@gmail.com Reporter: benoit.ro...@hoshikaze.net CC: steph...@mankowski.fr Target Milestone: --- I run Skrooge 2.8.1 on Ubuntu 16.04 LTS using KDE fw 5.18.0, Qt 5.5.1 and xcb. My main Skrooge file is around 9 MB large. Since migrating to Skrooge 2.8.1 from the previous version I got from Ubuntu standard software repos (don't remember which one it was), I noticed that, when validating an operation's category, Skrooge freezed a few split-seconds, along with a CPU surge briefly maxing out one core. Then I switched all my data to NAS (Thecus N3200 over 1 Gbps) to share them over several computers, including of course the Skrooge data. Now the freeze and CPU max-out last several seconds, I roughly measured from 15s to 30s. I've searched for such issue, FAQ indicates to disable balance computing, I did it, it didn't improve anything and I need balances, so I re-enabled them. My best (wild) guess is for a cumulative effect of 3 factors : - Never removed history over several years (just learned it could be done !), - Migration from Ubuntu's older Skrooge to 2.8.1, - Added network latency. I'll first try removing the history (but I'm currently doing my accounting and just stopped a couple minutes to file this bug report, so I'll do it afterwards and post the result as a follow-up. For the rest I have no idea... Thanks if anyone has... -- You are receiving this mail because: You are watching all bug changes.
