Bug 73397 - Kontact from 3.1.95 much slower than 3.1.94
Summary: Kontact from 3.1.95 much slower than 3.1.94
Status: RESOLVED WORKSFORME
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-01-24 13:04 UTC by eli
Modified: 2004-01-24 19:10 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description eli 2004-01-24 13:04:09 UTC
Version:            (using KDE KDE 3.2.0)
Installed from:    Unlisted Binary Package
OS:          Linux

I'm perplexed... Kontact from 3.1.95 seems much slower than 3.1.94.
Comment 1 Thiago Macieira 2004-01-24 15:24:34 UTC
I'm sorry, but without some hard facts "it seems slower" isn't something we can fix. Are you sure both binaries were compiled with the same compiler options? Nothing else in your configuration has changed?
Comment 2 eli 2004-01-24 16:52:36 UTC
I have no idea with what compiler options either were compiled with. All that I can tell you, is that 3.194 was prepared by Fedora and 3.1.95 was compiled by the Kde-Redhat project.

One other thing that I can tell you, is that everything seems to get bogged down and rather badly, I might add if I have kontact running, If I quit kontact everything gets back up to speed. I will download their SRPM of kdepim and let you know that changes anything.

Any ideas from your end as to why this could happen might be very helpful.

Thanks
Comment 3 eli 2004-01-24 18:39:42 UTC
Just tried to delete some things from my home and /tmp directories.

From my home folder
/.kde/~cache*.local
/.kde/~socket*.local
/.kde/~tmp*.local
/.mcop
.ICEauthority
.Xauthority

From /tmp
/kde-eli
/ksocket-eli
/mc-eli
/mcop-eli
/orbit-eli
and a couple of other files that contained eli in the name.

The response of Kontact became much quicker. I'll let you know in a couple of days and if things seem stable, I will mark this report resolved on my own. Thanks
Comment 4 eli 2004-01-24 19:10:34 UTC
Found the problem.... It wasn't yours after all. I was having an additional problem with artd. It turns out that if I had hardware detection on auto CPU usage for artd hovered around 50% as soon as I specified the alsa driver CPU usage went back down to normal and Kontact  behaved like it was supposed to. So I'm going to mark this resolved. Thanks for your patience.