Did I make a mistake?

[emef]

Hello everyone,
A few weeks ago, I bought a "SSD" disc of several hundreds of gigas on which I transferred the program "IM5" in itself and also the cache and the catalog, in directories Separated of course. I expected an acceleration of performances, but alas, it's just the opposite that happens: the smallest action takes a long time to take place, the view of the photo viewer is very slow and I pass Almost more temp to wait until Imatch returns my hand than anything else. Could this be due to having the catalog and cache on the same disk as the application itself?   
Thank you in advance for your opinion.

[jch2103]

Can you clarify just what you did? For example, is the SSD your new C drive? When you say you transferred the IM5 program, did you reinstall it on the drive? Etc.

[Mario]

Moving the database to an SSD always results in a massive performance improvement.
Something is clearly wrong on your new system.

Did you install IMatch normally on the new system by running the installer?

Did you relocate your drives in the database?
This is required because all your files are now on a different disk.
You should see no yellow off-line icons for folders or files in the database.

Do you use  a virus checker? If so, did you exclude the folder containing the database?

After moving the cache files to the SDD, did you check that IMatch uses that folder for Caching (Edit > Preferences > Cache).

Please ZIP and attach an IMatch log file (Help > Support > View Log file) (see log file in the iMatch help for more info).
This will tell us more about how IMatch is performing.

[emef]

Hello everyone,
I have my new "SSD" since the end of November 2016. At the time of its start, I contented myself before copying the contents of my old disk (H) on the new, then, with the disk manager of Windows , I re-assigned the letter "H" to the new disc. Of course, new versions of Imatch were installed normally with the installer.

I do not think I needed to relocate anything, my photos being on my "E" drive. The cache file is well marked on the "H".

Here are two log files (in zip format) dated 23/02 (day of strong slowdown) and this morning (24/02) where the cheeses appear faster (but I do not understand why).

Thank you for your patience.

[Mario]

The first log file just shows IMatch starting, loading the database (3 seconds) and then shutting down.

The second log file shows IMatch creating cache images in the background.
This takes about 5 to 7 seconds for each file, which appears to be rather quite slow.

[emef]

Thanks Mario.
It seems to me too slow  , what could be the cause?

[Mario]

No "slow" operations are recorded in the log files.
IMatch needs 4 seconds to load your database (OK) and the only slow thing is the creation of cache images. This is slow. But it should be much faster once IMatch has created all cache images.

Which of the operations you performed in these sessions did you experience as "slow"? Your database is very small and it should just "fly".

Did you check that your virus checker is leaving the folder containing the database alone?

[emef]

I use KIS 2016, and I told him not to monitor the activities of Imatch, besides placing the directory containing the database out of scanning.

[Mario]

You did not tell us which operations you consider slow.
According to the log file, the only operation which took more than one second was the loading of the database.
And a category update (but that's done in the background) and the creation of cache images.

[emef]

For example, when I double-click on a photo to display the slide show, the mouse cursor turns on itself for several seconds and sometimes, impatient, I click mechanically once or twice more, when l The image finally appears in the slide show, it jumps directly a few images further, giving me the impression that it reel furiously to catch up the delay. I did not have that impression before.

[Mario]

Your log file shows no information about you running the slide show or the Viewer.
Please enable the debug logging (Help > Support > Debug Logging) and then perform the operation you described.
Then attach the log file.


When you open files in the Viewer and there are no cache files (as it seems from the log file) IMatch has to create them.
Since generating one cache file on your machine takes 4 to 5 seconds, this can cause some delay. The Viewer needs a few images to start with.
Once the cache files have been generated, there should be almost no delay.

[emef]

Ok Mario, I think I understood where the problem comes from: since I transferred my base, cache and so on, on the new disc, I had not yet re-display images dating back several years (I was working on the last two years) and it is by wanting to modify / or add new data on the oldest photos that j I noticed this delay.

We'll leave it at that for now, and I'll come back and shout for help if the same symptoms persist after allowing IM5 to recalculate its caches.

Thank you for looking into my case.