Bug 511758

Summary:	digikam is almost unusable when mysql is not connected over lan
Product:	[Applications] digikam	Reporter:	Petr Schonmann <pschonmann>
Component:	Database-Mysql	Assignee:	Digikam Developers <digikam-bugs-null>
Status:	REPORTED ---
Severity:	normal	CC:	metzpinguin
Priority:	NOR
Version First Reported In:	8.8.0
Target Milestone:	---
Platform:	Appimage
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Petr Schonmann 2025-11-07 09:26:02 UTC

Hi, i dont know how to describe my problem precisely, but i try. Its probably my specific issue and i dont know how to debug or go better

My idea is central mysql on db.lan server which i can reach over whole lan ( wifi, eth ) and vpn.

But when i have connection over vpn or wlan
for example VPN ping to db.lan

time=9.92 ms
time=9.96 ms
time=9.03 ms
time=8.39 ms
time=8.30 ms
time=14.4 ms
time=12.2 ms
time=8.40 ms

vs lan

time=1.15 ms
time=0.889 ms
time=0.638 ms
time=0.726 ms
time=0.862 ms


using digikam is pain.
For example. When im in faces and all thumbs for faces  are loading, whole digikam is freezing until all mysql request are done. This is for all mysql related operations.

I know limitation for response because im not over cable and response from mysql is almost ~12x slower over vpn ~4x over wlan but should this be improved in some way ? Some caching mechanism, idk, its for discuss.

Now im using 12.1.1+maria~deb13

Comment 1 Maik Qualmann 2025-11-07 11:40:48 UTC

With a ping of 10ms, it's clear what the problem is. Imagine you want to load 1000 images in one view; that would already be 10 seconds just for the communication. And digiKam has to load much more than that. digiKam already uses extensive caching of items and many other things.

Here are the requirements from the documentation:

https://docs.digikam.org/en/setup_application/database_settings.html#the-mysql-remote-server
https://docs.digikam.org/en/setup_application/database_settings.html#database-type-criteria

Maik