Bug 310050 - MYSQL : Slow database performance after canceling a large duplicate image search
Summary: MYSQL : Slow database performance after canceling a large duplicate image search
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Database-Mysql (show other bugs)
Version: 2.9.0
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-13 20:03 UTC by zeronullity
Modified: 2017-12-18 21:18 UTC (History)
2 users (show)

See Also:
Latest Commit: https://commits.kde.org/digikam/2b8021b2d95ee1ebb10b385dae2744f0339c7bd0
Version Fixed In: 5.8.0

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description zeronullity 2012-11-13 20:03:27 UTC 
Database Driver : QMYSQL
Slow performance after canceling a large duplicate image search, even after restarting digikam constantly,
doing a right click on a image takes a long time including most other functions. The only way around this is to delete $user/.kde4/share/config/digikamrc and re-add the MYSQL database & image directories... then performance is fully restored. Also I would like to see searches split into multiple threads as it takes forever to do searches in large databases... perhaps adding a number of threads to options would be great.

Reproducible: Always

Steps to Reproduce:
1. Do a duplicate file search on a large database 100k or more files.
2. Cancel Duplicate File search in progress.
3. Performance grinds to a halt.
Actual Results:  
Very slow performance selecting images, right clicking etc.. 

Expected Results:  
Same performance as when the database was first created.

Fuzzy & Duplicate Image search is slow please add options to add more threads and fix this bug. - Thanks
Comment 1 zeronullity 2012-11-13 20:30:19 UTC 
I thought I would also add after the search is canceled... the duplicate search boxed is greyed out and you can do no more searches until digikam is restarted. However performance is still sluggish until digikamrc is deleted and database/image directory is re-added.
Comment 2 caulier.gilles 2014-07-17 19:37:14 UTC 
This entry still valid using last digiKam 4.1.0 ? 

Gilles Caulier
Comment 3 caulier.gilles 2016-07-06 19:42:00 UTC 
This file still valid using last digiKam 5.0.0 ?

Gilles Caulier
Comment 4 caulier.gilles 2016-07-16 05:57:21 UTC 
Swati,

This file is relevant of Mysql backend and must be checked for 5.0.0 release...

Gilles
Comment 5 caulier.gilles 2017-12-13 22:42:47 UTC 
With next 5.8.0 release Mysql support have been well improved and a lots of
bugs fixed.

Please test with pre release 5.8.0 bundles that we provide and give us a
feedback

https://files.kde.org/digikam/

Thanks in advance

Gilles Caulier
Comment 6 Maik Qualmann 2017-12-18 21:18:37 UTC 
Git commit 2b8021b2d95ee1ebb10b385dae2744f0339c7bd0 by Maik Qualmann.
Committed on 18/12/2017 at 21:16.
Pushed by mqualmann into branch 'master'.

add cancel function to the duplicate image search
FIXED-IN: 5.8.0

M  +5    -0    libs/database/dbjobs/dbjob.cpp
M  +2    -0    libs/database/dbjobs/dbjob.h
M  +5    -0    libs/database/dbjobs/duplicatesprogressobserver.cpp
M  +1    -0    libs/database/dbjobs/duplicatesprogressobserver.h
M  +5    -0    libs/database/haar/haariface.cpp
M  +4    -0    libs/database/haar/haariface.h
M  +4    -1    utilities/maintenance/duplicatesfinder.cpp

https://commits.kde.org/digikam/2b8021b2d95ee1ebb10b385dae2744f0339c7bd0