https://bugs.kde.org/show_bug.cgi?id=397110
Bug ID: 397110
Summary: Time to render filters is too long with MYSQL
Product: digikam
Version: 5.9.0
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Albums-Filters
Assignee: digikam-bugs-n...@kde.org
Reporter: erme...@gmail.com
Target Milestone: ---
Hi there,
I'm on Ubuntu 18.04 and use the Digikam 5.9 appimage.
After encountering some integrity issues with my tags tree, I migrated to mysql
to benefit of the InnoDB (5.7.23-0ubuntu0.18.04.1, locally listening)
My database is composed of two collections, one locally stored, another one
stored on a CIFS network share.
It is composed of 25k pictures, 66% as raw files, the remaining files are
shared between JPG, and movies files.
I'm a bit surprised of the time taken by applying filters: it will takes more
than 5 minutes to display 480 pictures: During this period, CPU usage of MySQL
reach 100% and digikam CPU usage is aroun 40%.
My MYSQL configuration don't use sockets, and is quite the default one except
the max_allowed_packet which has been improved for the digikam usage to 128M.
I had a look on the queries made to view if there are some improvements I could
do to improve the digikam usage and I saw that most of the time is spent when
doing the following statement (1358841 queries):
SELECT object
FROM ImageRelations
INNER JOIN Images ON ImageRelations.object=Images.id
WHERE subject=? AND type=2 AND status!=3
But I have only 4 records in the ImageRelations table.
Perhaps there is some technical improvments which could be done on this part.
Kind regards
--
You are receiving this mail because:
You are watching all bug changes.
