[digiKam-users] Anyone with a +300K photos internal mysql database?

[Rob Dueckman]

I have found that the majority of the startup time is spent reading the
similarity database.
Startup takes about 8 minutes on a image collection of about 400K
images.  Most of the time is spent on the query "SELECT value FROM
ImageSimilarity WHERE ( imageid1=? OR imageid2=? ) AND algorithm=?
..."  (I don't have any of the query after the ?.  Sorry)
Nothing is logged to the console while reading the database.If I
replace the similarity database with a blank one, startup is reduced to
about 34 seconds.
If I re-build the database, start up times are again slow.
This is running DK6 Beta2 Oct 15 release.
Rob


On Fri, 2018-10-19 at 08:22 +0000, Dumelle, Timo (E+K) wrote:
> I am dropping in here.
> I have 305k photos in many folders on a network share.Many of the
> folders on that share don't contain pictures, but since the paths are
> kinda "mixed up" with other files I can't just scan the photos.
> Dk needs about 5 - 10 minutes to start up while hanging on "reading
> database"And nearly every operation that goes beyond just viewing
> pics in albums cause it to either not responding for a long time or
> crashingCurrently it is finding duplicates which seems to proceed
> pretty fast.
> Picasa for example has absolute no problems with this pictures. But I
> need server functions for about 20 clients to connect to the DB
> Can I help with any of these tests?
> -----Ursprüngliche Nachricht-----Von: Digikam-users <
> digikam-users-bounces at kde.org> Im Auftrag von Rafael LinuxGesendet:
> Freitag, 24. August 2018 00:54An: digikam-users at kde.org
> Betreff: Re: [digiKam-users] Anyone with a +300K photos internal
> mysql database?
> Maik, as I wrote to Gilles, I can't see how many folders cause the
> user is on holidays this week, and I have no access to it, but I
> estimate that could be+13k albums, mostly with JPG photos.
> I want to thank you your test, cause I was sure that the reason of
> the issues weren't in the hardware or the database (mysql process
> never fired up any CPU core).
> If I can help anyway, let me know, but take into account that I can't
> do any test in any moment, cause the real system is not mine, so I
> have not access to it at my own  
> 
> 
> --Sent from: 
> http://digikam.1695700.n4.nabble.com/digikam-users-f1735189.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20181019/d7d099c3/attachment.html>