Bug 131376 - serious performances drop between kde 3.1 and 3.5
Summary: serious performances drop between kde 3.1 and 3.5
Status: RESOLVED WORKSFORME
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-07-26 02:16 UTC by johnny
Modified: 2008-12-06 14:55 UTC (History)
2 users (show)

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 johnny 2006-07-26 02:16:18 UTC
Version:           3.5.3 (using KDE KDE 3.5.3)
Installed from:    Fedora RPMs
Compiler:           from official fedora rpm package kdepim-3.5.3-0.1.fc4
OS:                Linux

I was using KOrganizer from kde 3.1. After a *long* period I upgrade my Linux distribution to Fedora Core 4, which ships KDE 3.5.3

Even with previous upgrades, I always copied my "ics" file as-is and all went fine. But with the last upgrade I noticed a serious performance drop while moving, resizing, creating, and deleting events (basically doing any change operation).

Currently my ics looks like this:

[johnny@satyr korganizer]$ ls -l std.ics
-rw-r--r--  1 johnny johnny 380010 Jul 26 01:48 std.ics
[johnny@satyr korganizer]$ cat std.ics | wc -l
19599

I think some internal algorithm changed its complexity from the number of records point of view, or something. Have you got any idea?

Thank you
Regards
Comment 1 Allen Winter 2006-09-12 01:37:11 UTC
johnny,

Are you noticing these performance problems with the KDE 3.5.4 KOrganizer?
I'm pretty sure we fixed a least one big performance issue in the 3.5.4 release.
Comment 2 johnny 2006-09-26 12:29:51 UTC
Well, now i'm running kde 3.5.4 compiled from sources. Unfortunately I suspect that some performance was gained from the compilation, because when I posted this issue i was running fedora distribution kde. Other applications are faster too.

It looks that at least resizing and moving events doesn't take so longer as before. Maybe the fix you mentioned is actually important.

Anyway as I mentioned I have a very big schedule, and I suspect that some operations (like selecting an event?) are O(n) instead of O(1) in the number of total events. Is that possible?

Thanks
Comment 3 Allen Winter 2006-09-26 18:23:07 UTC
In summary you seem to be saying that it is faster, but still is not fast enough ??

Comment 4 johnny 2006-09-28 01:25:47 UTC
Yeah..something like that!

No, seriously.. I'm saying that imho some operations are dependent from the size of the schedule file while they should not. Can you confirm that you are doing this in the code?

(like writing the whole file for a change?)
Comment 5 Reinhold Kainhofer 2006-11-02 19:21:06 UTC
Reassigning all KOrganizer bug reports and wishes to the newly created 
korganizer-devel mailing list.
Comment 6 Sergio Martins 2008-12-06 05:11:58 UTC
IMHO, korganizer from kde4 is faster than the one in kde3 (except month view, but we already got an open bug for that).

Maybe this could be closed now, we can't even measure how much faster it got.

(Unless someone installs KDE 3.1 and makes some benchmarks :))
Comment 7 Christophe Marin 2008-12-06 14:55:19 UTC
Indeed, closing this bug.