[Digikam-devel] [Bug 271841] digikam very slow when editing iptc data

[Nicolas Pomarede]

https://bugs.kde.org/show_bug.cgi?id=271841


Nicolas Pomarede <npomarede at corp.free.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |npomarede at corp.free.fr




--- Comment #7 from Nicolas Pomarede <npomarede corp free fr>  2011-08-30 21:49:33 ---
Hello

running digikam from the console, I got a lot of traces that explain waht is
happening : each time I modify some iptc tags in one image, the whole album is
completly rescanned. All other images (that were not modified) are read again,
which cause major slowdown.
Worse, it seems that if I modify iptc in several image in one go (let's say 7
images), then the album is rescanned 7 times in parallel, which certainly cause
a lot of disk accesses.

This is still with digikam 1.9.0 and kde 4.6.4, I haven't tried digikam 2 yet,
maybe this issue was fixed in 2.0 ?

Here're the trace when I modify iptc in one image :

digikam(371)/KEXIV2 KExiv2Iface::KExiv2::setIptcTagsStringList:   : 
Iptc.Application2.LocationCode  =>  MEX
digikam(371)/KEXIV2 KExiv2Iface::KExiv2::setIptcTagsStringList:   : 
Iptc.Application2.LocationName  =>  Mexique
digikam(371)/KEXIV2 KExiv2Iface::KExiv2::setIptcTagsStringList:   : 
Iptc.Application2.Byline  =>  Nicolas Pomarede
digikam(371)/KEXIV2 KExiv2Iface::KExiv2::setIptcKeywords:   ==> Iptc Keywords: 
Personnes,Mexique
digikam(371)/KEXIV2 KExiv2Iface::KExiv2::KExiv2Priv::saveToFile: File
Extension:  "jpg"  is supported for writing mode
digikam(371)/KEXIV2 KExiv2Iface::KExiv2::save: Metadata for file ' DSCF4130.JPG
' written to file.
digikam(371)/digikam (core) Digikam::DImg::load:
"/home/npomarede/Images/Photos/DSCF4044.JPG"  : JPEG file identified
digikam(371)/digikam (core) Digikam::isJpegImage: mimetype =  "JPEG"
digikam(371)/KEXIV2 KExiv2Iface::KExiv2::getImageOrientation: Orientation =>
Exif.Image.Orientation =>  1
digikam(371)/digikam (core) Digikam::DImg::load:
"/home/npomarede/Images/Photos/DSCF4045.JPG"  : JPEG file identified
digikam(371)/digikam (core) Digikam::DImg::load:
"/home/npomarede/Images/Photos/DSCF4046.JPG"  : JPEG file identified
digikam(371)/digikam (core) Digikam::DImg::load:
"/home/npomarede/Images/Photos/DSCF4048.JPG"  : JPEG file identified
digikam(371)/digikam (core) Digikam::DImg::load:
"/home/npomarede/Images/Photos/DSCF4050.JPG"  : JPEG file identified
digikam(371)/digikam (core) Digikam::DImg::load:
"/home/npomarede/Images/Photos/DSCF4053.JPG"  : JPEG file identified
digikam(371)/digikam (core) Digikam::DImg::load:
"/home/npomarede/Images/Photos/DSCF4054.JPG"  : JPEG file identified
digikam(371)/digikam (core) Digikam::DImg::load:
"/home/npomarede/Images/Photos/DSCF4055.JPG"  : JPEG file identified
digikam(371)/digikam (core) Digikam::DImg::load:
"/home/npomarede/Images/Photos/DSCF4056.JPG"  : JPEG file identified
digikam(371)/digikam (core)
Digikam::ScanControllerLoadingCacheFileWatch::slotImageChanged: 9158
"/home/npomarede/Images/Photos/DSCF4044.JPG"
digikam(371)/digikam (core)
Digikam::ScanControllerLoadingCacheFileWatch::slotImageChanged: 9159
"/home/npomarede/Images/Photos/DSCF4045.JPG"
digikam(371)/digikam (core)
Digikam::ScanControllerLoadingCacheFileWatch::slotImageChanged: 9160
"/home/npomarede/Images/Photos/DSCF4046.JPG"

This continues until all images in that album are rescanned (320 in that case).
When this is done, digikam becomes responsive again.

Nicolas

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.