Full sync spinning its wheels?

[DavidHoffmanuk]

I started a full scan of my (230k images) catalog an hour ago and it reached 92% after about 10 minutes. It's been stuck there since with pm-task using about 100% CPU. Is it still likely to complete or should I force quit?
Mac Pro 10.14.6

Thanks!
David Hoffman

[Kirk Baker]

David,

I started a full scan of my (230k images) catalog an hour ago and it reached 92% after about 10 minutes. It's been stuck there since with pm-task using about 100% CPU. Is it still likely to complete or should I force quit?

I would not suggest forcing a quit.  You could try just quitting the app.  If it still fails to quit then you could force quit.

I'd like to see your logs though.  Please post them.

-Kirk

[DavidHoffmanuk]

To my surprise PM+ did quit without forcing and when I tried it again the full sync ran for quite a while (I was doing other things so not sure) but continuously and to a conclusion so maybe this was just a one off glitch. I've attached the log anyway.

Thanks
David

[DavidHoffmanuk]

I don't know if it's connected but when I was getting the logs I noticed 30 GB of files in that folder. I've attached a screenshot - is there anything I can trash?

David

[Kirk Baker]

David,

To my surprise PM+ did quit without forcing and when I tried it again the full sync ran for quite a while (I was doing other things so not sure) but continuously and to a conclusion so maybe this was just a one off glitch. I've attached the log anyway.

Some of the holdup was the process producing the proxies was accessing images (DNGs) that had no preview and thus no proxy could be generated.  I think these may be DNGs from an iPhone which apparently does not embed any previews.  You can run those through the Adobe DNG Converter and it can put in large JPEG previews which will then correct the problem.

Some of the holdup was that some of the images were malformed and their metadata could not be parsed, and some had access permission issues (or simply that the file no longer existed at the path where it was found during the scan).

-Kirk

[Kirk Baker]

David,

I don't know if it's connected but when I was getting the logs I noticed 30 GB of files in that folder. I've attached a screenshot - is there anything I can trash?

You can delete anything there that ends in '.log'

You still have CATALOG_DEBUG_LOGGING turned on and it will generate a significant amount of data over time.  You can turn that off and the logs will only contain errors and warnings and should remain much smaller.

-Kirk

[Kirk Baker]

You can also delete the cache and Render folders but make sure that Photo Mechanic Plus is not running when you do so.  You will be losing out on some performance (in the case of the Render folder) when you view those images again.

You can control the size of those caches in the Preferences.  More cache space isn't always better.

-Kirk

[DavidHoffmanuk]

I deleted the cache & render folders. Inside the cache folder was a 'catalog' folder with more cache & render folders inside. Is that normal?

I've not yet noticed a performance loss.

I often look at, sort and change metadata on groups of images of around 7,000 px on the long side. The render cache is 16,000 MB. Is that reasonable?

Debug logging is off but I only remembered to turn it off a week or so ago. Maybe you're seeing an old log?

David

[Kirk Baker]

David,

I deleted the cache & render folders. Inside the cache folder was a 'catalog' folder with more cache & render folders inside. Is that normal?

Yes.

I've not yet noticed a performance loss.

If you were still rendering RAW (at least I think you were before), the impact would be significant, but only when visiting images that were in the Render cache that are no longer there.

I often look at, sort and change metadata on groups of images of around 7,000 px on the long side. The render cache is 16,000 MB. Is that reasonable?

What kind of images are they and do they have embedded previews or do they have to be rendered to be seen?

Debug logging is off but I only remembered to turn it off a week or so ago. Maybe you're seeing an old log?

The dyn.1.log that was included was older and did have CATALOG_DEBUG_LOGGING on.  The most recent dyn.log file did not appear to have the flag enabled.

-Kirk