[digikam] [Bug 362023] Extremely slow metadata writing via maintenance

https://bugs.kde.org/show_bug.cgi?id=362023 Maik Qualmann changed: What|Removed |Added Version Fixed In||7.7.0 Status|REPORTED

[digikam] [Bug 362023] Extremely slow metadata writing via maintenance

https://bugs.kde.org/show_bug.cgi?id=362023 soredake changed: What|Removed |Added CC||ndrzj1...@relay.firefox.com -- You are receiving

[digikam] [Bug 362023] Extremely slow metadata writing via maintenance

https://bugs.kde.org/show_bug.cgi?id=362023 --- Comment #20 from caulier.gil...@gmail.com --- Maik, Why this file still open even the comment from comment #18 ? Gilles -- You are receiving this mail because: You are watching all bug changes.

[digikam] [Bug 362023] Extremely slow metadata writing via maintenance

https://bugs.kde.org/show_bug.cgi?id=362023 --- Comment #19 from caulier.gil...@gmail.com --- digiKam 7.0.0 stable release is now published: https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ We need a fresh feedback on this file using this version. Best Regards Gilles

[digikam] [Bug 362023] Extremely slow metadata writing via maintenance

https://bugs.kde.org/show_bug.cgi?id=362023 caulier.gil...@gmail.com changed: What|Removed |Added Component|Metadata|Maintenance-Metadata -- You are

[digikam] [Bug 362023] Extremely slow metadata writing via maintenance

https://bugs.kde.org/show_bug.cgi?id=362023 --- Comment #18 from Mario Frank --- Git commit 2f8ddd42ef62d7aea9e490cdb05ffcc644810c81 by Mario Frank. Committed on 22/02/2017 at 15:05. Pushed by mfrank into branch 'master'. Merged the current state of the garbage

[digikam] [Bug 362023] Extremely slow metadata writing via maintenance

https://bugs.kde.org/show_bug.cgi?id=362023 caulier.gil...@gmail.com changed: What|Removed |Added Version|5.0.0 |5.4.0 -- You are receiving this

[digikam] [Bug 362023] Extremely slow metadata writing via maintenance

https://bugs.kde.org/show_bug.cgi?id=362023 --- Comment #17 from Simon --- Hi Gilles, This problem is still the same. I reduced it for me by using internal mysql database and preloading most of the database to memory. When testing with appimage, sqlite on system hd and data

[digikam] [Bug 362023] Extremely slow metadata writing via maintenance

https://bugs.kde.org/show_bug.cgi?id=362023 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment

[digikam] [Bug 362023] Extremely slow metadata writing via maintenance

https://bugs.kde.org/show_bug.cgi?id=362023 Bizy changed: What|Removed |Added CC||koen.b...@gmail.com --- Comment

[digikam] [Bug 362023] Extremely slow metadata writing via maintenance

https://bugs.kde.org/show_bug.cgi?id=362023 --- Comment #14 from Simon --- Indeed, my setup is far from optimal for disk io. I have both the database and the images on a ntfs pratition of a hard disk on my laptop (at least not system hd). I thought that the database would

[digikam] [Bug 362023] Extremely slow metadata writing via maintenance

https://bugs.kde.org/show_bug.cgi?id=362023 --- Comment #13 from Maik Qualmann --- This is are long waiting times, up to 5 seconds until a scan is completed for one image. Disabling the scanning does not help, he would be rescheduled in any case. Modification date or file

[digikam] [Bug 362023] Extremely slow metadata writing via maintenance

https://bugs.kde.org/show_bug.cgi?id=362023 --- Comment #12 from Simon --- Created attachment 98665 --> https://bugs.kde.org/attachment.cgi?id=98665=edit Command line output in the middle of writing metadat to files with scancontroller2.patch I applied the patch and added

[digikam] [Bug 362023] Extremely slow metadata writing via maintenance

https://bugs.kde.org/show_bug.cgi?id=362023 --- Comment #11 from Simon --- Created attachment 98664 --> https://bugs.kde.org/attachment.cgi?id=98664=edit Startup of digikam and start of writing metadata with scancontroller2.patch -- You are receiving this mail because:

[digikam] [Bug 362023] Extremely slow metadata writing via maintenance

https://bugs.kde.org/show_bug.cgi?id=362023 --- Comment #10 from Simon --- Do I apply this patch on top of the current HEAD or on top of your previous patch? I guess the first, but just to be sure. On 27/04/16 21:14, Maik Qualmann via KDE Bugzilla wrote: >

[digikam] [Bug 362023] Extremely slow metadata writing via maintenance

https://bugs.kde.org/show_bug.cgi?id=362023 --- Comment #9 from Maik Qualmann --- Created attachment 98651 --> https://bugs.kde.org/attachment.cgi?id=98651=edit scancontroller2.patch That it is now slowly working because now images are processed with symbolic links.

[digikam] [Bug 362023] Extremely slow metadata writing via maintenance

https://bugs.kde.org/show_bug.cgi?id=362023 Maik Qualmann changed: What|Removed |Added Attachment #98521|0 |1 is obsolete|

[digikam] [Bug 362023] Extremely slow metadata writing via maintenance

https://bugs.kde.org/show_bug.cgi?id=362023 --- Comment #8 from Simon --- And the scan is now going clearly slower than before the patch. I am now running it almost two days and its at 3% only. -- You are receiving this mail because: You are watching all bug changes.

[digikam] [Bug 362023] Extremely slow metadata writing via maintenance

https://bugs.kde.org/show_bug.cgi?id=362023 --- Comment #7 from Simon --- Created attachment 98528 --> https://bugs.kde.org/attachment.cgi?id=98528=edit Command line output in the middle of writing metadat to files with scancontroller.patch -- You are receiving this mail

[digikam] [Bug 362023] Extremely slow metadata writing via maintenance

https://bugs.kde.org/show_bug.cgi?id=362023 --- Comment #6 from Simon --- Created attachment 98527 --> https://bugs.kde.org/attachment.cgi?id=98527=edit Startup of digikam and start of writing metadata with scancontroller.patch -- You are receiving this mail because:

[digikam] [Bug 362023] Extremely slow metadata writing via maintenance

https://bugs.kde.org/show_bug.cgi?id=362023 --- Comment #5 from Simon --- Thanks for looking into this. I applied your patch. The results seems to be the same (maybe somewhat less frequent rescans). I attached the initial part of the log after startup, where redundant stuff

[digikam] [Bug 362023] Extremely slow metadata writing via maintenance

https://bugs.kde.org/show_bug.cgi?id=362023 --- Comment #4 from Maik Qualmann --- Created attachment 98521 --> https://bugs.kde.org/attachment.cgi?id=98521=edit scancontroller.patch Can you try this test patch? And report how digiKam now behaves. Maik -- You are

[digikam] [Bug 362023] Extremely slow metadata writing via maintenance

https://bugs.kde.org/show_bug.cgi?id=362023 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com

[digikam] [Bug 362023] Extremely slow metadata writing via maintenance

https://bugs.kde.org/show_bug.cgi?id=362023 --- Comment #2 from Maik Qualmann --- Git commit 773f9361e5df5904c938ad9ee4cbb19acd1aa1f6 by Maik Qualmann. Committed on 21/04/2016 at 19:03. Pushed by mqualmann into branch 'master'. fix absolute file path without symbolic

[digikam] [Bug 362023] Extremely slow metadata writing via maintenance

https://bugs.kde.org/show_bug.cgi?id=362023 --- Comment #1 from Simon --- Created attachment 98490 --> https://bugs.kde.org/attachment.cgi?id=98490=edit Command line output of writing metadata to files. -- You are receiving this mail because: You are watching all bug