Version: (using KDE KDE 3.5.0) Installed from: Ubuntu Packages (2 minutes and 27 seconds on a very fast computer, to be exact). Kopete takes a very long time to start up with a particular configuration. It will get as far as displaying its main window with toolbar icons and a menu, and then become unresponsive for over two minutes. I don't think this is normal behaviour, (and if it is, it shouldn't be). So I ran valgrind/callgrind against the kopete with the configuration that takes a very long time to start up, and a control one one which starts up in a reasonable amount of time. Valgrind generated two output files for each kopete; the second one of each seemed to be the important one. In the long-time start-up, there is a susipicious pattern: Over ten million calls to QListViewItem::compare, and twenty million calls to KopeteMetaContactLVI::key (QListViewItem::compare seems to be calling KopeteMetaContactLVI::key twice for each call to itself). In the control start-up, there are less than twenty thousand calls to QListViewItem::compare, and thirty thousand calls to KopeteMetaContactLVI::key. As this is a factor of 500 less, it could easily account for the long start-up time. If anyone wants the valgrind/callgrind output file, it is 490 K when bzip2'd up.
how many groups and contacts do you have?
No groups; about a thousand contacts listed in the contact list (half of which seem to be empty).
Is the statistics plugin enabled? # grep "statistics" ~/.kde/share/config/kopeterc kopete_statisticsEnabled=true
The statistics plugin is not enabled. If you're interested, here's the plugin section from the config file: [Plugins] kopete_aimEnabled=true kopete_aliasEnabled=false kopete_autoreplaceEnabled=false kopete_connectionstatusEnabled=false kopete_contactnotesEnabled=false kopete_cryptographyEnabled=false kopete_highlightEnabled=false kopete_historyEnabled=true kopete_msnEnabled=true kopete_nowlisteningEnabled=false kopete_texteffectEnabled=true kopete_translatorEnabled=true kopete_webpresenceEnabled=false
Hi, Turn off kopete_statisticsEnabled, solve my problem... But i like this feature, is possivel to fix this show plugin?
*** Bug 133057 has been marked as a duplicate of this bug. ***
disabling the statistic plugin (in the gui of kopete) made my kopete speed up from about 2 minutes to 2 seconds. I heard others reporting the same. I would like to suggest to turn the statistics plugin off by default, untill the startup delay has been solved..
Statistics is no longer enabled by default.
but it will still take two minutes to start if it is enabled and the database is big enough.
Okay, will move bug to statistics plugin and address there.
*** Bug 119529 has been marked as a duplicate of this bug. ***
SVN commit 773881 by cconnell: Optionally show date of messages in chatwindow FEATURE:117989 M +4 -1 kopete/chatwindow/chatmessagepart.cpp M +72 -27 kopete/config/behavior/behaviorconfig_chat.ui M +4 -0 libkopete/kopetebehaviorsettings.kcfg WebSVN link: http://websvn.kde.org/?view=rev&revision=773881
That was the wrong bug number, sorry.
Kopete 0.50.80 with enabled statistics plugin takes not more than 5sec to start. So seems to be fixed with KDE 4.1
Kopete svn trunk r835161 with enabled Statistics plugin doesnt take longer than 5 sec to start here, too. But i dont have a large enough db to test, so i cant tell if the size of the db matters.
Got this problem on kde4-kdenetwork-kopete-4.3.4-1.i686. iotop shows about 250KB/s transfer on kopete_statistics-0.1.db (~35MB) for few minutes. App disconnects from jabber network, and is unresponsive.
I can confirm Piotr. After using Kopete some time with statistics, it becomes slower, especially at going offline. I think the module should be removed until the bug is solved, because some friends of mine got the bug too. And here is someone else: http://forum.ubuntuusers.de/topic/kopete-benoetigt-ewig-zum-starten/ Maybe bug 182587 is a duplicate of this.
Confirmed here. Thank god, I had some free time and found it was the statistics plugin, It was slow as hell since KDE4.0 release. (It took 2mins of my life for a year and I did not notice :/ ) My kopete_statistics-0.1.db is now 30,2 megabytes. Disabling it works for me too.
*** Bug 233640 has been marked as a duplicate of this bug. ***
I'm lucky I found this page, and finally turned off that bloody thing (statistics plugin). This plugin needs some optimization or rewrite from scratch.
*** Bug 247887 has been marked as a duplicate of this bug. ***
SVN commit 1225336 by lvsouza: Backporting r1225335 to 4.6.2: Use kapp->processEvents() to minimize statistics plugin blockage. This does not solve the problem, Kopete feels sluggish when loading statistics plugin even after this change (CPU still goes to 100% usage), but it is better than blocking Kopete altogether. CCBUG: 117989 M +3 -0 statisticsplugin.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=1225336
Actually I had not used Kopete since a few years (!) as it always took lots of minutes to start, eating all cpu time during this period, and I considered it to be simply broken. Disabling the statistics plugin helped imediately. I'd vote for a big, fat warning in the plugin's description which cannot be missen before enabling it...
SVN commit 1227533 by lvsouza: Per metacontact statistics DB is created only when contact goes online or when statistics for an offline metacontact is requested. This improves plugin startup and shutdown times and also helps with UI responsiveness. Now shutdown time is proportional to the number of metacontacts that went online since Kopete has started plus the number of offline metacontacts that the user requested statistics from. That is better then being proportional to the number of all metacontacts registered but is not that good yet. BUG: 117989, 138903 CCBUG: 246785 FIXED-IN: 4.6.3 M +34 -2 statisticsplugin.cpp M +2 -0 statisticsplugin.h WebSVN link: http://websvn.kde.org/?view=rev&revision=1227533
SVN commit 1227534 by lvsouza: Backporting 1227533 to 4.6 branch: Per metacontact statistics DB is created only when contact goes online or when statistics for an offline metacontact is requested. This improves plugin startup and shutdown times and also helps with UI responsiveness. Now shutdown time is proportional to the number of metacontacts that went online since Kopete has started plus the number of offline metacontacts that the user requested statistics from. That is better then being proportional to the number of all metacontacts registered but is not that good yet. BUG: 117989, 138903 CCBUG: 246785 FIXED-IN: 4.6.3 M +34 -2 statisticsplugin.cpp M +2 -0 statisticsplugin.h WebSVN link: http://websvn.kde.org/?view=rev&revision=1227534
*** Bug 138903 has been marked as a duplicate of this bug. ***
I don't have the statistics plugin enabled, and it still takes nearer 10 minutes to start up while eating 100% CPU.
@bigjools: This could be problem in kabc akonadi plugin (there is problem with global mutex or something similar). Try to remove akonadi plugin from contact resources via: $ kcmshell4 kresources
Git commit 5f8ffd33235276beb5ebcbdac8c422b6250381de by Pali Rohár. Committed on 12/05/2014 at 22:05. Pushed by pali into branch 'master'. Turn off synchronous mode for sqlite database in statistics plugin Synchronous mode does not have any real advantages here and only slow down writes to database. When it is turned off it can dramatically speed up kopete statistics plugin when changing status from online to offline or on exit. Tested with 150MB big database: before patch: exit time about 10s after patch: exit time about 1s M +10 -0 plugins/statistics/statisticsdb.cpp http://commits.kde.org/kopete/5f8ffd33235276beb5ebcbdac8c422b6250381de
Git commit d9a25c460cf1777eb2555cd8df72609800b25e20 by Pali Rohár. Committed on 12/05/2014 at 22:05. Pushed by pali into branch 'KDE/4.13'. Turn off synchronous mode for sqlite database in statistics plugin Synchronous mode does not have any real advantages here and only slow down writes to database. When it is turned off it can dramatically speed up kopete statistics plugin when changing status from online to offline or on exit. Tested with 150MB big database: before patch: exit time about 10s after patch: exit time about 1s M +10 -0 plugins/statistics/statisticsdb.cpp http://commits.kde.org/kopete/d9a25c460cf1777eb2555cd8df72609800b25e20
*** Bug 219695 has been marked as a duplicate of this bug. ***