Digikam slow at startup

[Kenneth Ingham-2]

I explored the fuzzy match options in Digikam, and, ever since then,
Digikam takes a while to start up.  During startup, top shows it is
using 100% of one CPU for around 60 seconds. 

I am running 5.6.0 on OpenSUSE Tumbleweed on a x86_64 i7 system.  Should
I put this into bugzilla?

--
Kenneth

A people that values its privileges above its principles soon loses both.
---Dwight D. Eisenhower, First Inaugural Address, January 20, 1953

[Gilles Caulier-4]

Hi,

Before, please try with 5.7.0 Linux AppImage bundle :

https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM

Gilles Caulier

2017-09-01 16:34 GMT+02:00 Kenneth Ingham <[hidden email]>:

> I explored the fuzzy match options in Digikam, and, ever since then,
> Digikam takes a while to start up.  During startup, top shows it is
> using 100% of one CPU for around 60 seconds.
>
> I am running 5.6.0 on OpenSUSE Tumbleweed on a x86_64 i7 system.  Should
> I put this into bugzilla?
>
> --
> Kenneth
>
> A people that values its privileges above its principles soon loses both.
> ---Dwight D. Eisenhower, First Inaugural Address, January 20, 1953
>
>

[Kenneth Ingham-2]

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

[Gilles Caulier-4]

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 <[hidden email]>:

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

[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 <[hidden email]>:

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

[Mario Frank]

Hey Kenneth,

after digging and testing the code tonight, I could isolate the problem.
We solved the problem for duplicates search some time ago. This time,
it's the fuzzy image search. I will take this opportunity to make some bigger
refactoring on the fuzzy searches part as a quick fix could lead to other bugs
in that subsystem. The complexity of the fuzzy subsystem increased a lot due
to numerous extensions and optimisations in the last 2 releases.
So I'll do some clean up and stabilise the whole fuzzy subsystem.

I will inform you when I am done.

Regards,
Mario

Am 25.09.2017 um 15:38 schrieb 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 <[hidden email]>:

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