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

Simon bugzilla_noreply at kde.org
Fri Nov 25 23:30:52 GMT 2016


--- Comment #17 from Simon <freisim93 at gmail.com> ---
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 on separate hd
(no ssl in my laptop :) ), now even the UI gets unresponsive during
writing. Maybe it would be more efficient to remember which files were
written and issue a rescan after writing of metadata is done?
Generally the only issue I have with syncthing is its constant scanning
of stuff on the HD. Whenever I start it causes tons of read access (to
images, not database) producing command line output like
"digikam.dimg***: JPEG file identified" and "digikam.metaengine:
Orientation => Exif.Image.Orientation => 1", as if these files were new
or modified (they are not).


On 25/11/16 15:38, bugzilla_noreply at kde.org wrote:
> https://bugs.kde.org/show_bug.cgi?id=362023
> caulier.gilles at gmail.com changed:
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                  CC|                            |caulier.gilles at gmail.com
> --- Comment #16 from caulier.gilles at gmail.com ---
> What's about this file using digiKam AppImage bundle 5.4.0 pre release given at
> this url :
> https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM
> Gilles Caulier

You are receiving this mail because:
You are the assignee for the bug.

More information about the Digikam-devel mailing list