https://bugs.kde.org/show_bug.cgi?id=247141
Summary: unreasonable long working time when writing "Metadata in Files" Product: digikam Version: 1.2.0 Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general AssignedTo: [hidden email] ReportedBy: [hidden email] Created an attachment (id=49946) --> (http://bugs.kde.org/attachment.cgi?id=49946) screen shots Version: 1.2.0 (using KDE 4.4.2) OS: Linux Hello: when I write "all metadata in files" (total number 66570 files), it takes 07.22.24 h with a AMP - CPU (please compare with attached screenshot) Would be very nice to speed up!! Thank you- Axel Further Details: digiKam version 1.2.0 AVI: 59 BMP: 1 GIF: 100 JPG: 41431 PNG: 168 RAW-CR2: 629 RAW-CRW: 10897 RAW-DNG: 2 RAW-NEF: 13146 TIFF: 137 Gesamtzahl der Einträge: 66570 : Alben: 847 Stichwörter: 21 Reproducible: Always Steps to Reproduce: irrelevant -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
https://bugs.kde.org/show_bug.cgi?id=247141
Marcel Wiesweg <[hidden email]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |UPSTREAM --- Comment #1 from Marcel Wiesweg <marcel wiesweg gmx de> 2010-08-17 12:29:48 --- Metadata writing is 100% done by exiv2, so any improvements must be done in that component. It would be advisable to have a recent version installed. Even with all optimizations, metadata writing requires read+write hard disk access, which is always slow. Additionally, some formats may require rewriting of larger chunks of the file, depending on the applied changes. But that's the field of experts like Andreas Huggel. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Axel Krebs
https://bugs.kde.org/show_bug.cgi?id=247141
Gilles Caulier <[hidden email]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[hidden email], | |[hidden email] --- Comment #2 from Gilles Caulier <caulier gilles gmail com> 2010-08-17 12:32:27 --- I set Andreas in copy for info... Gilles Caulier -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Axel Krebs
https://bugs.kde.org/show_bug.cgi?id=247141
--- Comment #3 from Andreas Huggel <ahuggel gmx net> 2010-08-17 13:27:17 --- Which version of Exiv2 are you using? There was a severe performance issue when writing to images with certain Nikon Makernotes in version 0.19 (http://dev.exiv2.org/issues/show/677). It is fixed in 0.20. I'm not aware of any other performance problems. Andreas -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Axel Krebs
https://bugs.kde.org/show_bug.cgi?id=247141
--- Comment #4 from Axel Krebs <axel krebs t-online de> 2010-08-19 15:48:41 --- Hello Andreas: this is the component information: digiKam version 1.2.0 Exiv2 kann in JP2 speichern: Ja Exiv2 kann in JPEG speichern: Ja Exiv2 kann in PGF speichern: Keine Exiv2 kann in PNG speichern: Ja Exiv2 kann in TIFF speichern: Ja Exiv2 unterstützt XMP-Metadaten: Ja LibCImg: 130 LibExiv2: 0.19 LibJPEG: 62 LibJasper: 1.900.1 LibKDE: 4.4.2 (KDE 4.4.2) LibKExiv2: 1.0.0 LibKdcraw: 1.0.0 LibLCMS: 118 LibPGF: 6.09.44 LibPNG: 1.2.42 LibQt: 4.6.2 LibRaw: 0.8.5 LibTIFF: LIBTIFF, Version 3.9.2 Copyright (c) 1988-1996 Sam Leffler Copyright (c) 1991-1996 Silicon Graphics, Inc. Marble-Funktion: 0.9.2 Parallelisiertes Entfernen von Mosaikmustern: Ja LibGphoto2: 2.4.8 LibKipi: 1.0.0 Following this information, I have LibExiv2 0,19 --- QUESTION: Why do I need to write _all_ meta-data at one time? When building thumbs, I can choose a _fast_ option "suchen" _or_ a slow option "alle neu erzeugen". This distinction could be the solution I am thinking of!! I believe, it is partly a matter of indexing _strategy_, _not_ only a potential bug in a library, DIGIKAM-authers can't change themselves. Can you agree? Why don't offer a fast "meta-data-indexing" just for those pics, one just puts in ones collection? I mean, just monitoring the _differences_, not the total of _all_ pics!! This could even happen automatically in the background, I guess. In this case, the indexing speed is surely of secondary interest, because not bottlenecking work anymore. --- Sorry for the answer delay! I hope these considerations may help- Axel --- Am 17.08.2010 13:27, schrieb Andreas Huggel: > https://bugs.kde.org/show_bug.cgi?id=247141 > > > > > > --- Comment #3 from Andreas Huggel <ahuggel gmx net> 2010-08-17 13:27:17 --- > Which version of Exiv2 are you using? > There was a severe performance issue when writing to images with certain Nikon > Makernotes in version 0.19 (http://dev.exiv2.org/issues/show/677). It is fixed > in 0.20. I'm not aware of any other performance problems. > > Andreas > -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Axel Krebs
https://bugs.kde.org/show_bug.cgi?id=247141
--- Comment #5 from Marcel Wiesweg <marcel wiesweg gmx de> 2010-08-23 21:01:28 --- There is already a wish for something that can be called deferred metadata writing, that all files which need writing are marked as such. In addition to the current two choices: 1) Write immediately after each change 2) Write to all at once, you would have then 3) Write to all which have been changed. Can be solved with an internal tag, we'll have these in 2.0. I dont quite understand the connection to indexing. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Axel Krebs
https://bugs.kde.org/show_bug.cgi?id=247141
[hidden email] changed: What |Removed |Added ---------------------------------------------------------------------------- Component|general |Metadata-Engine -- You are receiving this mail because: You are the assignee for the bug. |
Free forum by Nabble | Edit this page |