Bug 447072 - digiKam waiting long time, if collection is huge.
Summary: digiKam waiting long time, if collection is huge.
Status: RESOLVED DUPLICATE of bug 411099
Alias: None
Product: digikam
Classification: Applications
Component: Searches-Engine (show other bugs)
Version: 7.4.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-12-16 12:54 UTC by Peter
Modified: 2021-12-30 09:09 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter 2021-12-16 12:54:34 UTC
SUMMARY
I have a collection, this contain 300.000 elements. I use digikam 7.4, local Samba file server and mysql database to store the collection, and I have 5 users. I would like a button the start search, because if the collection is huge, digikam seems it freez (digikam working, but there is no feedback on the process). The user is horrified not to know what is happening!
This is because: If I select search function on the left panel, digikam repeats the last search, although it should not do so, only if requested by the user this. Digikam starts the search even if the user enters the word to search slowly, and does not wait for the user to finish writing. It is horrible! If the collection is huge, digikam seems it freez.
What I suggest: Search button on the New Search section. Digikam don't start the search immediately when the user click the search tab on the left panel, only in case if user clicking the Search button.

SOFTWARE/OS VERSIONS
Windows: Windows 10
Linux/KDE Plasma: Linux Mint 20.2 Cinnamon
Digikam: appimage
Comment 1 Maik Qualmann 2021-12-16 17:49:35 UTC

*** This bug has been marked as a duplicate of bug 411099 ***
Comment 2 Maik Qualmann 2021-12-16 17:55:24 UTC
It is not necessarily the search on the MySQL server, it is done relatively quickly. It only takes longer for them to be loaded from the DB if the result is a large number of items. In digiKam-7.4.0 we have the possibility to create the thumbnail database as a local SQLite file, this relieves the MySQL server significantly. You should try it out.

Maik
Comment 3 Peter 2021-12-16 19:22:36 UTC
Thanks your reply.

I do not use sqlite due to central data storage and backup (several people working on the collection).

411099 Bug report quote:
"This way, if I want to search, I'll click in "Search", no thumbnails should be showed, then I'll type the word(s) I want to search and finally I press 'Enter' key. Then, and only then, the thumbnails of the images that matches should be showed. That's my opinion as user."

I completely agree! This is correct behaviour!
Comment 4 Peter 2021-12-16 19:38:11 UTC
"But you know that you can disable the automatic search when typing text? Right mouse button menu in the input field."

I did not know this. The search experience is definitely better.
Comment 5 Peter 2021-12-16 20:03:28 UTC
> MySQL server significantly. You should try it out.
> 
> Maik

I'll try. Thank You Maik.
Comment 6 Peter 2021-12-17 11:37:26 UTC
Hi Maik.
So, I tested it: Thumbnails in SQLite, SQLite database on the local ssd disk, other database files in mysql server in the local network.
Result:
Thumbnail rebuild: 9 hour
Thumbnail display time when search: difference is imperceptible.
I decided, I will continue to use mysql, but thanks for the idea, I don't forget this.