[Digikam-users] lots of photos and startup time
opersonlig_postadress at hotmail.com
Thu Jul 9 11:04:52 BST 2009
Andi, I hope you adress me with Daniel, I think there are two Daniel in this tread. Appoligies if mistaken.
I have 260 000 images in my collection. As long as the collection is only indexed performance is OK. It is after working with the collection, moving files, renaming and it realy degrades when I use the find duplicates feature. I have a lot of duplicates as I have used the option of capturing in both JPG and CR2.
> From: andi.clemens at gmx.net
> To: digikam-users at kde.org
> Date: Thu, 9 Jul 2009 10:37:13 +0200
> Subject: Re: [Digikam-users] lots of photos and startup time
> Amarok is using embedded MySQL, but which also assumes you have installed
> mysql (but you need no server running in the background).
> my thumbsDB (ok this is not the normal digikam DB) is 900MB big, but it opens
> quite fast. So I don't know if this is really the issue here.
> how many items / images do you have in your database?
> In my current test collection, I have 200.000, but my database is only 180MB
> Maybe yours is really corrupted (or has a lot of old entries, that you might
> need to delete manually).
> If you have less images, you could try to remove all entries from the table
> "images" that have a status of 3 (deleted).
> On Thursday 09 July 2009 09:37:24 Daniel Bauer wrote:
> > Gilles,
> > I also followed this thread quitly (as I still use old digikam on old kde
> > 3.5 plus reiserfes...). But I fully support your idea to change the
> > database system, if this is causing the delay.
> > Here I have several very large MySql databases and they are very fast, but
> > digikam is always very slow on opening for the first time after logging in
> > as a user (also the newer digikam I installed in kde 4 for testing, I
> > thought it was kde4's fault...)
> > (Apart from the coding work) the only problem I see is that with MySql
> > users will have to install MySql too. While this is more or less one click
> > on Linux I don't know how it is on other systems.
> > Maybe there could be an option for the user: sqlite as a (slow) standard,
> > but working out of the box, and MySql as an option, if the user has
> > installed it and knows the path etc. Isn't amarok offering something
> > similar?
> > regards
> > Daniel
> > On Thursday 09 July 2009 08:45:31, Gilles Caulier wrote:
> > > Marcel, Andi,
> > >
> > > All this thread tell me that we need to found urgently a solution to
> > > this problem.
> > >
> > > If sqlite cannot drive large database, another DB backend need to be
> > > used. For me MySql sound like the right alternative, if performance
> > > are there of course (how to make a quick test about ?)
> > >
> > > About DB schema and all DB queries, it's really complicated to migrate
> > > from SQLite to MySql. SQL syntax is really different between both DB
> > > backend ?
> > >
> > > Gilles
> Digikam-users mailing list
> Digikam-users at kde.org
Vem är du? Gör personlighetstestet på MSN Dejting!
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Digikam-users