Bug 192258 - starting takes long time
Summary: starting takes long time
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Database-Scan (show other bugs)
Version: 0.10.0
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-10 19:55 UTC by Edwin Schepers
Modified: 2017-07-25 13:18 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In: 3.3.0
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Edwin Schepers 2009-05-10 19:55:55 UTC
Version:           0.10.0-rc2 (using KDE 4.2.0)
OS:                MS Windows
Installed from:    MS Windows

When I start digikam for the first time and I choose a photo directory with 3700 photo's, digikam needs 3 minutes to start. I think that's far too long. Maybe an option is to start digikam already while still reading the new photo's. That way, users can already enjoy while the database is being updated.

Regards,
Edwin
Comment 1 caulier.gilles 2009-05-10 20:40:21 UTC
Use stable release to test, not rc2...

Gilles Caulier
Comment 2 Martin Lubich 2009-05-14 11:20:33 UTC
I have the same behaviour with digikam 0.10.0 on KDE 4.2.2. Original packages from kubuntu 9.04 64bit.
Filesystem is reiserfs, 23000 photos take ~2 min initially on a AMD Phenom Quadcore @2.4Ghz, 8GB RAM.
Subsequent starts take under 1 sec to read the database.

digikam 0.9.x had no such behaviour with the same photo collection.
Comment 3 Marcel Wiesweg 2009-05-14 14:04:39 UTC
Gilles, isn't this fixed with the progress dialog / first run assistant changes you implemented recently?
Comment 4 caulier.gilles 2009-05-14 14:19:53 UTC
Fixed no... and i think that _first_ startup cannot be decreased very well, because we collect a lots of informations from items.

Sure, now with First Run assistant, user is aware about long process time during first run operation. Also, progress dialog is always displayed during first run, not splash. User has always a real progres feedback.

Gilles
Comment 5 Martin Lubich 2009-05-14 15:08:14 UTC
I think I made myself not clear when using the term 'first time', sorry about that.

With 'first time', I mean every first start of digikam after a reboot of my machine.

So every time I switch on my computer and start digikam I have to wait 2 min before I can work with my photos (splash screen is telling me its reading tshe dátabase) , and this I think is not ok. Each subsequent start of digikam is quite fast ( < 1 sec reading the database) as long as the computer stays switched on.
Comment 6 caulier.gilles 2011-12-15 09:02:58 UTC
Edwin,

This file still valid using digiKam 2.3.0 for windows ?

Gilles Caulier
Comment 7 Ananta Palani 2013-06-10 13:01:07 UTC
(In reply to comment #5)
> I think I made myself not clear when using the term 'first time', sorry
> about that.
> 
> With 'first time', I mean every first start of digikam after a reboot of my
> machine.
> 
> So every time I switch on my computer and start digikam I have to wait 2 min
> before I can work with my photos (splash screen is telling me its reading
> tshe dátabase) , and this I think is not ok. Each subsequent start of
> digikam is quite fast ( < 1 sec reading the database) as long as the
> computer stays switched on.

Martin,

Is this still a problem with the new 3.1.0 release?
   http://download.kde.org/stable/digikam/digiKam-installer-3.1.0-win32.exe

If you are no longer using digiKam please let us know as well
Comment 8 Martin Lubich 2013-06-10 13:08:19 UTC
(In reply to comment #7)
> (In reply to comment #5)
> > I think I made myself not clear when using the term 'first time', sorry
> > about that.
> > 
> > With 'first time', I mean every first start of digikam after a reboot of my
> > machine.
> > 
> > So every time I switch on my computer and start digikam I have to wait 2 min
> > before I can work with my photos (splash screen is telling me its reading
> > tshe dátabase) , and this I think is not ok. Each subsequent start of
> > digikam is quite fast ( < 1 sec reading the database) as long as the
> > computer stays switched on.
> 
> Martin,
> 
> Is this still a problem with the new 3.1.0 release?
>    http://download.kde.org/stable/digikam/digiKam-installer-3.1.0-win32.exe
> 
> If you are no longer using digiKam please let us know as well

This no no longer a problem with 3.1. It might have been a problem with my usage of reiserfs. 

And yes, I still do use digikam, almost on a daily base :)