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

[Maik Qualmann]

If the last used tab was the album tab, the virtual search albums will no 
longer be executed on startup in digiKam-6.0.0. Of course, if the last used 
tab was a search album, depending on the search, the start may take longer.

Another question to Rafael, how many albums does your collection have? From 
30,000 albums it is here with me slowly interesting, that can take dan already 
a few minutes. This is a problem we have not solved yet and where I see the 
problem internally in Qt. I'll check it again here with Qt-5.11.

Maik

Am Donnerstag, 23. August 2018, 08:51:56 CEST schrieb Gilles Caulier:
> Rafael,
> 
> I insist. Can you reproduce the problem when the scan at startup option is
> disabled. It's important because if the problem disapear, there is a chance
> to isolate the problem with virtual search album loading at startup.
> 
> Maik, you don't fix this problem in 6.0.0 ?
> 
> Another explainations about slow time loading at startup are given in this
> bugzilla file :
> 
> https://bugs.kde.org/show_bug.cgi?id=396086
> 
> Gilles Caulier
> 
> 2018-08-21 14:45 GMT+02:00 Rafael Linux <rafael.linux.user at gmail.com>:
> > Option about you ask for is enabled. But while Digikam is starting, the
> > "startup window" remains visible those seven minutes (if I don't click
> > that
> > startup window, cause in that case simply that startup window closes and I
> > don't know then if Digikam is loading or not).
> > 
> > Anyway, just after that startup window is automatically closed (after
> > seven
> > or more minutes) the status bar shows nothing about exploring anything.
> > It's
> > not doing any scan after that - or is so fast that I can't see it - , and,
> > as I said, "atop" doesn't show any massive reading from any application
> > (nor
> > Digikam) while Digikam is starting. So, IMHO, is not scanning related and
> > in
> > the case it were true, it should happen AFTER the startup window is
> > auto-closed and showed in the status bar as a progress bar.
> > 
> > 
> > 
> > --
> > Sent from: http://digikam.1695700.n4.nabble.com/digikam-users-> > f1735189.html