Bug 478075

Summary:	All database operations are far slower than with previous version
Product:	[Applications] digikam	Reporter:	IvorJ <ivorwjones>
Component:	Database-Mysql	Assignee:	Digikam Developers <digikam-bugs-null>
Status:	RESOLVED FIXED
Severity:	major	CC:	caulier.gilles, metzpinguin
Priority:	NOR
Version:	8.2.0
Target Milestone:	---
Platform:	Microsoft Windows
OS:	Microsoft Windows
Latest Commit:		Version Fixed In:	8.4.0
Sentry Crash Report:
Attachments:	attachment-1293038-0.html attachment-1294822-0.html

Description IvorJ 2023-12-04 20:17:01 UTC

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. Starting the Programme
2. 
3. 

OBSERVED RESULT
Painfully slow - takes several minutes.  Also slow on database operations e.g. modifying geolocation.  At least 10 times slower than previous version.  This version is virtually unusable.

EXPECTED RESULT
Always used to open far more quickly

SOFTWARE/OS VERSIONS
Windows: 11


ADDITIONAL INFORMATION
Using MariaDB as the MySQL option for the database.  An upgrade was performed when installing 8.2.0

Comment 1 Maik Qualmann 2023-12-04 20:45:37 UTC

The new version is based on Qt6 and was created with the Microsoft compiler. 
Please try the digiKam-8.2.0 version created like the previous ones.

https://download.kde.org/stable/digikam/8.2.0/digiKam-8.2.0-Qt5-Win64.exe

Personally, I cannot reproduce any issues with MySQL with our future Qt6 version.

Please give us feedback.

Maik

Comment 2 IvorJ 2023-12-04 20:53:01 UTC

Created attachment 163867 [details]
attachment-1293038-0.html

Thanks, that loaded much more quickly.

On Mon, 4 Dec 2023 at 20:45, Maik Qualmann <bugzilla_noreply@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=478075
>
> Maik Qualmann <metzpinguin@gmail.com> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>          Resolution|---                         |WAITINGFORINFO
>                  CC|                            |metzpinguin@gmail.com
>              Status|REPORTED                    |NEEDSINFO
>
> --- Comment #1 from Maik Qualmann <metzpinguin@gmail.com> ---
> The new version is based on Qt6 and was created with the Microsoft
> compiler.
> Please try the digiKam-8.2.0 version created like the previous ones.
>
> https://download.kde.org/stable/digikam/8.2.0/digiKam-8.2.0-Qt5-Win64.exe
>
> Personally, I cannot reproduce any issues with MySQL with our future Qt6
> version.
>
> Please give us feedback.
>
> Maik
>
> --
> You are receiving this mail because:
> You reported the bug.

Comment 3 IvorJ 2023-12-04 21:08:47 UTC

Created attachment 163871 [details]
attachment-1294822-0.html

The geolocation also works much more quickly.

On Mon, 4 Dec 2023 at 21:04, Maik Qualmann <bugzilla_noreply@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=478075
>
> Maik Qualmann <metzpinguin@gmail.com> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>          Resolution|WAITINGFORINFO              |---
>              Status|NEEDSINFO                   |REPORTED
>
> --
> You are receiving this mail because:
> You reported the bug.

Comment 4 Maik Qualmann 2023-12-06 07:09:14 UTC


*** This bug has been marked as a duplicate of bug 477853 ***

Comment 5 caulier.gilles 2023-12-26 15:17:31 UTC

Hi all and Merry Christmas time with your family

This file is duplicate one. From the root file, we found a solution to fix time latency under windows introduced with 8.2.0.

Following the comment: https://bugs.kde.org/show_bug.cgi?id=477853#c102

... It sounds working fine now.

Please test and report digiKam 8.3.0 pre-release installer for Windows available at this file:

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

Thanks in advance

Gilles Caulier

Comment 6 caulier.gilles 2024-03-28 15:44:38 UTC

Fixed with bug 477853