Hi Mario
Today a wondered, why IMatch loads quite slow, I had the impression.
Then I have seen some of the entries with "ptc-camera", like
12.04 08:21:42+78516 [12DC] 02 I> ptc-camera
12.04 08:21:42+ 0 [12DC] 02 I> file.ext
12.04 08:22:57+75687 [12DC] 02 I> city
12.04 08:23:00+ 2266 [12DC] 02 I> file.ext
12.04 08:23:00+ 0 [12DC] 02 I> city
12.04 08:23:00+ 0 [12DC] 02 I> ptc-camera
12.04 08:23:00+ 0 [12DC] 02 I> ptc-camera
What is ptc-camera? I have never spotted this, but I have overseen it maybe.
Log attached (74K)
IMatch takes a very long time (157s!) to initialize the caches used for various purposes...
Didn't we have the same problem already once with your database?
IMatch and IMWS manage many in-memory caches to speed up things.
IMWS keeps track of which caches were used in the previous IMatch session and then re-fills the last 10 caches used during startup the next time.
This can slow down the startup a few seconds (usually) but makes everything else perform faster.
The caches are loaded in the background, don't usually cause and locks on the database.
For a database with 250,000 files this will require quite a bit of database activity, but it should not interfere with loading IMatch.
My largest database has now 480,000 files and I never noticed a delay of more than 4 seconds caused by the cache pre-load.
Can you please repeat your test with debug logging enabled? This will add more details to the log.
When you rename the file
"C:\ProgramData\photools.com\IMatch6\config\imws-storage.db"
IMatch should start fast again (no caches pre-loaded anymore). But all the stored settings of the apps you use will be missing (App Manager, VarToy etc.) so this can only be a test.
Thanks, Mario,
I will do so (new log).
Just now I have unfortunately a familiar case of death to deal with, hence no time now.