Slow after latest update

[theresamarie1]

I am experiencing the same behavior I experienced a couple of weeks ago after updating the software. It's now 1 hour past the time I updated the software, and I'm still unable to use the tool as it's doing something called 'reading metadata' and is unresponsive on a very fast machine with lots of SSD.  The reading metadata jumps between 31 hours and 63 hours and has been at 1% for 10 minutes.   I thought this might be a one time thing from my prior post, but it seems not.  It's not using much CPU, like 4%, or memory (20%), nor is it using all of the disk bandwidth, but is unresponsive and unusable.   I do have a large database, which is showing 230K images now, although it's treating thumbnails like images so there is some redundancy.    On the top bar is says IMATCH Databased.imd5 (not responding).  I haven't added more data to the database this is just after updating the software and the new software needed to update the database and whatever else it needs to do.
Helpful suggestions welcome.

[Mario]

Please always include the log file in ZIPped form when you report any problem with IMatch.
This gives us a minimum of information to work with. See log file

it's doing something called 'reading metadata' and is unresponsive on a very fast machine with lots of SSD. 

IMatch is ingesting images. 
If the time estimate varies that much, file sizes or formats vary.
What kind of files are you processing, where are they stored?

Are you a new user or an old user who has upgraded from IMatch 2023?
Did you make an exception for IMatch and the database folder in your virus checker?

I do have a large database, which is showing 230K images now, although it's treating thumbnails like images so there is some redundancy.   

Not sure what you mean by "thumbnails as images". IMatch manages one thumbnail per file in the database, and ten for each video.

I'll know more when you attach the log file.
You can make a copy of it while IMatch is running. Open the TEMP folder on your system and select the log file and press Ctrl+C, Ctrl+V. Then ZIP the copy and attach. See log file.

Ps.: 
When you refer to a "previous post", please link to it. My memory is good, but I cannot remember everything. Your previous post may be from weeks ago!

Also, please press <Enter> once in a while. Your post has no paragraphs and is a wall of text when read on a smart phone.

[theresamarie1]

There is no imatch log file in my temp directory, in fact my TEMP directory is empty.
I did copy the log file from the support tab, here is a link to the zipped file: https://drive.google.com/open?id=1VWlyqGbjoX2r8LcHny0BnMTcD0dIU6CT&usp=drive_fs

I have used Imatch for a long time.. not sure when I began, but it was more than a decade.

There are many file sizes and formats for cameras I have used over 25 years of images.  Many different raw formats, TIFs and JPGs.

The files are all on fast Samsung SSDs, multiple drives.    64GB of memory, Threadripper AMD 16 core processor.

Well, the .THMs are showing as individual files in the database in some cases.   I don't recall it doing this in the past but now seems to have expanded some folders to show .THMs as files in my 2002 and 2003 raw image folders.

My post a couple of weeks ago is on March 15th when I first upgraded to 2025.  I don't know how to reference the post in a link.

Terri

[Mario]

There is no imatch log file in my temp directory, in fact my TEMP directory is empty.

Most likely you looked in the wrong TEMP directory. IMatch does not run without a log file.
Open your (not the Windows!) TEMP folder by typing

%TEMP% into the Windows address bar.

Or open it from the Dashboard. The Info Panel has a button for this.

.THM files were used by older digital cameras, when I recall correctly. The files contain their own metadata, or, at least for older Canon models, they contain the metadata for the RAW file. If you don't want these files in the database, you can exclude the file format: File Formats

I don't know how to reference the post in a link.

Right-click the data above your post to copy the link into the clipboard, then paste into your post so others know which post you refer to:



You can also copy & paste the link shown in the address bar of your web browser. Whatever is more comfortable.

Note: You can attach files up to 5MB in size directly to your posts.
No need to use Google Drive for a 1MB file and force me to give Google my IP address and have to clear all the 400KB of cookies Google Drive has planted in my browser.

[Mario]

Now, having all of that out of the way, let's look at your log file.

The first thing I see is a very large number of folders which have been found to be externally modified and have been scheduled by IMatch for indexing.

I'm sure you have read the release notes, but here is the info why this can happen again for your convenience:

https://www.photools.com/release-notes?search=2661

As it happens, many folders on your system were detected and are now processed. Search your log file for FolderSweeper: Folder to find the names of all affected folders.

The log file contains 579 warnings in only 5K lines. A lot.

ExifTool reports issues like
"Error creating file: C:/Users/Terri/AppData/Local/Temp/imt_et_2540172904629358.xmp" which is strange and rare.
It also reports many issues with broken maker notes, invalid CanonSettingsData  etc. Not uncommon when many (older) images are indexed which have been processed by who-knows-what in the old days.

A larger number of "invalid file formats" or "unsupported" file format entries.

Many warnings from WIC about unknown file formats, unsupported RAW formats and stuff.

I have attached a text file with all warnings and errors below, which shows you which files were affected.

While processing some of your files, the memory consumption of IMatch rises to 25 GB, which is a lot. But your system has 64 GB and 59GB were available when IMatch started, so this is OK.
My guess would be that LibRaw or Windows WIC choked on some of your files and allocated tons of memory. Broken or unsupported files sometimes cause this effect.

Of course each file failing to load slows down IMatch, and sometimes, when files are failing to load, it takes Windows 10 or 30 seconds to figure out that it cannot load a file.

Your PC reports 32 processor cores, which means IMatch will index at least 32 files in parallel, depending on the performance profile you have enabled.

If the IMatch and/or the WIC subsystem become unresponsive while processing so many "problem" files in parallel, I suggest you reduce the performance profile (Edit > Preferences > Application) to the "Low" setting until IMatch has chewed all these files.

Also, again, make sure you have made an exception for IMatch in your virus checker.
TODO #1 on this list: Welcome to IMatch 2025!