iMatch freezes for ~1 minute

[Carlo Didier]

Here are the relevant lines from the log (complete log attached):

Code Select Expand

07.31 13:54:59+    0 [0E08] 50  M>                 > 16 PTMetabase::GetWriteBackFiles  'PTMetabase.cpp(12575)'
07.31 13:56:17+77594 [0E08] 03  I>                # Process Memory Info: WSC: 628MB, WSP: 628MB (NEW PEAK), PF: 1585038

This happened when I selected some 20-30 dng files in iMatch and clicked on my favourites shortcut for Photoshop CC 2014. They opened in ACR where I did nothing (I decided to do differently what I wanted to do). Coming back to iMatch, it was frozen with the "hourglas" showing for about 1 minute. Bottom left status line said "Reading P:\Photos René". None of the previously selected images was in that folder tree and no files were changed there.

System is a dekstop with Coer i5 CPU, 8GB RAM, 2TB data HD, 250GB SSD for system, programs and iMatch databases. Lots of space on every disk.

I tried to reproduce this with the task manager open, but nothing happened this time. But it's not the first time I have these "white-outs" and I can't find a common point to when they happen.

[attachment deleted by admin]

[Mario]

I just wrote a longer response about this:

https://www.photools.com/community/index.php?topic=3015.msg19650#msg19650

IMatch took over 70 seconds (!) to calculate the files with pending write-back. And your database is not that big (80 K files). On my old system (SSD) IMatch takes between 7 and 15 seconds for the same operation on a 120,000 files database.

IMatch needs to calculate this info only once, so if will happen only once per session. And even if you close and re-open IMatch, it will be much faster the next time, unless Windows flushes the file system cache entirely (or your reboot).

[Carlo Didier]

... to calculate the files with pending write-back.

Ah, that reminds me of the 11000 files for which iMatch wants to write back keywords that I don't want any more. Could that be the reason why it takes so long?

[Mario]

The number of results found does not affect the runtime. My 120,000 files database has over 40,000 files with pending keyword and other metadata updates.

If you like, you can reset this state by reloading the metadata for these files (Shift+Ctrl+F5 > Rescan Metadata) or by using the Database > Tools > Reset Processing Queues. If you do the rescan, make sure protection of unwritten data is off under Edit > Preferences > Metadata.