Very, very slow tagging

[Maik Qualmann]

Do you use a local drive or a network drive on which the images are? The used 
time from the image scanner are very very long.

Maik

Am Freitag, 3. November 2017, 18:59:13 CET schrieb digikam at 911networks.com:
> OK:
> 
> The file is available at:
> https://drive.google.com/open?id=0B7HTmJCO2gG7OWFOUGtGTEFNTFE
> 
> It starts at line: 386
> 
> ................................................
> digikam.general: Writting tags
> digikam.general: -------------------------- New Keywords ("animals", "dogs",
> "dog photography") digikam.metaengine: xmlACDSee "<Categories><Category
> Assigned=\"1\">animals</Category><Category
> Assigned=\"1\">dogs</Category><Category Assigned=\"1\">dog
> photography</Category></Categories>" digikam.metaengine:
> "/photos/digikam/streets/dogs/dogs-2016/dogs-vancouver-20160630-2812.cr2" 
> ==> Read Iptc Keywords:  () digikam.metaengine:
> "/photos/digikam/streets/dogs/dogs-2016/dogs-vancouver-20160630-2812.cr2" 
> ==> New Iptc Keywords:  ("animals", "dogs", "dog photography")
> digikam.metaengine: MetaEngine::metadataWritingMode 2
> digikam.metaengine: Will write Metadata to file
> "/photos/digikam/streets/dogs/dogs-2016/dogs-vancouver-20160630-2812.cr2"
> digikam.metaengine: wroteComment:  false
> digikam.metaengine: wroteEXIF:  true
> digikam.metaengine: wroteIPTC:  true
> digikam.metaengine: wroteXMP:  true
> ................................................
> 
> then by line: 786:
> 
> ................................................
> digikam.database: Scanning took 5156 ms
> digikam.metaengine: File time stamp restored
> digikam.metaengine: Metadata for file "dogs-vancouver-20160409-1631.cr2"
> written to file. digikam.metaengine: Will write XMP sidecar for file
> "dogs-vancouver-20160409-1631.cr2" digikam.general: Detected change,
> triggering rescan of "/photos/digikam/streets/dogs/dogs-2016/"
> digikam.metaengine: wroteComment:  false
> digikam.metaengine: wroteEXIF:  true
> digikam.metaengine: wroteIPTC:  true
> digikam.metaengine: wroteXMP:  true
> digikam.metaengine: File time stamp restored
> digikam.metaengine: Metadata for file "dogs-vancouver-20160409-1631.cr2"
> written to XMP sidecar. digikam.general: Detected change, triggering rescan
> of "/photos/digikam/streets/dogs/dogs-2016/" digikam.database: Starting
> scan!
> digikam.database: Finishing took 3731 ms
> [Thread 0x7ffee7fff700 (LWP 4684) exited]
> 
> .......................................................................
> 
> Then the scanning takes longer and longer...
> 
> .......................................................................
> Database stats:
> 
> digikam version 5.7.0
> Images:
> JPG: 191
> RAW-CR2: 2188
> RAW-RAF: 558
> total: 2937
> 
> Total Items: 2937
> Albums: 12
> Tags: 32
> 
> Database backend: QSQLITE
> Database Path: /photos/photos/
> ...............................................................
> 
> On Fri, 3 Nov 2017 11:53:14 +0100
> 
> Simon Frei <freisim93 at gmail.com> wrote:
> > If you can reproduce it, run digikam in gdb and hit ctrl-c after a
> > while of such high activity. Then get the backtrace ("bt") and send
> > the result
> > - there hopefully is a clue what it is doing.
> > 
> > On 03/11/17 00:27, digikam at 911networks.com wrote:
> > > It's been running for 2 hours and 29 minutues and it's still
> > > running!
> > > 
> > > Help!
> > > 
> > > On Thu, 2 Nov 2017 14:11:16 -0700
> > > 
> > > digikam at 911networks.com wrote:
> > >> DK 5.7.0 (sqlite) on archlinux with 12gb RAM, AMD 8350 (8 cores)
> > >> 
> > >> I just tagged 2365 images with 1 tag and now it's "stuck"
> > >> 
> > >> HTOP: 6 cores: 100% and 2 cores 99.7% & 99.8%) no disk IO, no
> > >> swap.
> > >> 
> > >> HTOP: memory used: 1.42G from 11.7G
> > >> 
> > >> It's been like that for the last 25 minutes.
> > >> 
> > >> Any way to speed this up?
> > >> 
> > >> 
> > >> vyS