Summary: | serious performances drop between kde 3.1 and 3.5 | ||
---|---|---|---|
Product: | [Applications] korganizer | Reporter: | johnny |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | christophe, smartins |
Priority: | NOR | ||
Version First Reported In: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
johnny
2006-07-26 02:16:18 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. 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 In summary you seem to be saying that it is faster, but still is not fast enough ?? 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?) Reassigning all KOrganizer bug reports and wishes to the newly created korganizer-devel mailing list. 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 :)) Indeed, closing this bug. |