Bug 242639 - Korg very slow on start up
Summary: Korg very slow on start up
Status: RESOLVED FIXED
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: SVN trunk (KDE 4)
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-23 23:25 UTC by Sabine Faure
Modified: 2011-02-14 21:09 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 Sabine Faure 2010-06-23 23:25:05 UTC
Version:           SVN trunk (KDE 4) (using Devel) 
OS:                Linux

Korg needs about 1 minutes and 30s to launch a kolab and Imap resource and 9 Ical calendar files and the Birthdays and Anniversaries calendar.

Reproducible: Always

Steps to Reproduce:
- Go to K menu
- Type in 'Korg' in the Search menu
- Click on 'Korganizer'

Actual Results:  
- Korg main dialogue appears immediately but its resource and folder view is only displaying 1 calendar and it is impossible to display any menu or to click on any button
- after 22s the ical calendar appear with a loading symbol next to them (ring of dots that cannot even move because it is so slow)
- after 57s the loading symbols finally start to move
- after 1 minute and 15s the Ical files are loaded (the loading symbol disappear)
- after 1 minute and 30 the Birthday and Anniversaries calendar is loaded

Trunk, Svn Rev 1141839

Expected Results:  
This is a regression since last time I tested this it took a lot less time to launch.


Also I think it would be a good idea to create a progress bar so that the user sees that the programme is launching (nobody looks at the resources and folders view while Korg launches so the user may not realize that he cannot click on buttons or open menus because the resources and folders view is not done loading yet) and does not wonder why Korg is frozen on launch.
Comment 1 Andreas Kahnt 2010-11-15 16:17:26 UTC
17 cpu seconds are required to add a new meeting from klick-to-ok to next-action-possible while kontact uses 100% cpu as the own running process on a dual core 1.8GHz HP nx9420 laptop running Ubuntu-10.10/KDE-4.5.1/KOrganizer-4.4.6.
And another 17s to delete and redisplay November. To change monthly display from November 2010 to October 2010 neede about 28 cpu seconds.
I've about 450 events: 240 in one and 10 in another calendar plus 200 birthdays/anniversaries. Nepomuk and akonadi services are running but they don't need much cpu power.
Other PIM solutions, ie evolution, require less than one second for the same task.
Comment 2 Sergio Martins 2011-02-14 21:09:22 UTC
This was fixed, it was a bug related to holidays.

Please retest in current git master.