Digikam slow at startup

[Mario Frank]

Hey Kenneth,

sorry for the long delay. I just had some time trying to reproduce your
problem.
In fact I could reproduce it. The problem seems to be that the last
fuzzy image search
you did is retreived on startup. We had that problem fixed some time ago
but it seems
to pop up again. This seems to be a regression. I will dig into the code
as soon as I can.

As a workaround, try the following.
Start digikam, go into the fuzzy image search and set the lower
threshold to 90 and the upper to 100.
Then do a fuzzy image search on some image. Close digiKam and restart it.
The start should be much faster than.

Regards,
Mario

Am 02.09.2017 um 10:36 schrieb Gilles Caulier:
> Look in Setup/Misc digiKam panel. There are some option about database
> maintenance. There are enabled on your computer ?
>
> Gilles Caulier
>
> 2017-09-01 22:02 GMT+02:00 Kenneth Ingham <ingham at i-pi.com
> <mailto:ingham at i-pi.com>>:
>
>     The 5.7.0 appimage is still slow at startup.  It took 1 min, 55sec to
>     display the window when I started it at the command line.
>
>     Also, the messages on the terminal stopped for most of this time.  It
>     printed a bunch of messages ending with:
>
>     digikam.general: Added root album called:  "KIPHOTO"
>     digikam.general: Added root album called:  "Photos"
>
>     It was only a few seconds at most to get to this point.  It then was
>     silent for most of the 1:55, then continued with:
>
>     digikam.general: Using  8  CPU core to run threads
>     digikam.general: Action Thread run  1  new jobs
>
>     Once the console messages started up again, it was at most a short
>     delay
>     before the window appeared. 
>
>     --
>     Kenneth
>
>     A people that values its privileges above its principles soon
>     loses both.
>     ---Dwight D. Eisenhower, First Inaugural Address, January 20, 1953
>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20170925/ab3c3f7e/attachment.html>