https://bugs.kde.org/show_bug.cgi?id=382152
Stephane MANKOWSKI <steph...@mankowski.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDSINFO |ASSIGNED
Resolution|WAITINGFORINFO |---
--- Comment #13 from Stephane MANKOWSKI <steph...@mankowski.fr> ---
Hi,
This helps a lot.
Indeed, we can see that line:
virtual SKGAdviceList SKGPayeePlugin::advice(const QStringList&) ;1;
32888.54614 ; 32888.54614 ; 32888.54614 ; 32888.54614 ; 32888.54614 ;
32888.54614
It means that the computation of the advices around "Payee" took 32000 ms
(32s).
This is really interesting.
First: You certainly have a dashboard opened when you do a modification on
operation. On this dashboard, you have the "Advice" widget. This widget takes
time. So you have 2 workarounds:
1- You can close your dashboard when you do a modification but you will still
have bad performances when you will open it again.
2- You can remove the "Advice" widget from the dashboard.
Second: I published today a new version of Skrooge (2.9.0). On this version,
the dashboard is not refreshed when this is not the displayed page. This should
be better for you. It means that you don't have to close the dashboard when you
do a modification on operations but you will still have bad performances when
you will switch on dashboard.
Last: This could be interesting to find why the "Payee" advice has so bad
performances. Could you do that?
export SKGTRACESQL=10000
run skrooge, play you scenario and send me the traces (you should see the SQL
query causing issue)
Could you give me the number of payees you have in your document too?
Regards.
--
You are receiving this mail because:
You are watching all bug changes.
