Bug 215972

Summary: korganizer calendar via akonadi is very slow
Product: [Applications] korganizer Reporter: Octavian Petre <octavsly>
Component: generalAssignee: Sergio Martins <smartins>
Status: RESOLVED FIXED    
Severity: wishlist CC: octavsly, smartins
Priority: NOR    
Version: 4.3   
Target Milestone: ---   
Platform: Gentoo Packages   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Octavian Petre 2009-11-24 16:32:21 UTC 
Version:            (using KDE 4.3.3)
OS:                Linux
Installed from:    Gentoo Packages

I was setting up korganizer (via kontact) to use the akonadi resources. 
akonadi was configured to use several *ics files (coming from kde3.5).

While everything worked as expected, korganizer was very slow in the following situations:
- first use of the akonadi resource
- enabling disabling some calendars in the akonadi resource

If the *ics files were directly used in korganizer, the speed difference was more than 10x.

Is this a know issue?

Best regards,
Octavian

P.S. when using akonadi resources, a new calendar item is added to "a default calendar" instead of asking in what calendar should be added. Then I do not see an item to move it to another calendar.
Comment 1 Octavian Petre 2010-04-24 21:37:25 UTC 
KDE 4.4.2:  same issue
Comment 2 Sergio Martins 2011-01-23 15:00:58 UTC 
How many events do you have?

Is it slow loading or changing weeks?
Comment 3 Octavian Petre 2011-01-23 22:50:19 UTC 
Events (grepped on SUMMARY in the *.ics files) : 
 the biggest two calendars have 380 and 250. In total around 800.

 It is slow in both cases. I am even afraid to test it.
Comment 4 Sergio Martins 2011-01-23 22:55:05 UTC 
The development version of korganizer is akonadi based, i.e., it doesn't use the KRES<->akonadi bridge, which might be slow.

I'll test with a big calendar nevertheless.
Comment 5 Octavian Petre 2011-01-24 16:07:51 UTC 
What is KRES<->akonadi bridge? 
A good doc will also be sufficient
Comment 6 Octavian Petre 2011-06-21 22:35:50 UTC 
with kdepim-4.6.0 the issue is not anymore seen.

Closing the bug