The speed of execution of LR Classic CC decreases drastically by performing a simple treatment repeatedly

  • 1
  • Problem
  • Updated 9 months ago
Currently, I have to perform with LR Classic CC repetitively a simple treatment. Here is the sequence that I am following:
- Choose a photo (TIFF) in a collection.
- Edit this picture in PS. By applying two three corrections or actions and saving the photo under another name in JPEG format. - The rescue is done in the original directory of the base picture. - Back in LR and go to the original directory of the basic picture. - Synchronization of that directory in order to make appear the new picture. - Application of a new keyword. - This new keyword let appear the picture in a smart collection. - End of the loop. I repeat this action on +/- 100 photos per work sequence. I see a significant drop in synchronization speed, and display of the new picture. This drop is such that waiting times are so long that it becomes impossible to work effectively. I do not see a slowdown on PS. By cons, I see the available RAM start (+/- 21RAM) drastically reduce to arrive at values ​​of +/- 3 RAM There are about 50 permanent smart collections in this LR catalog. (which actually tends to slow down the database I'm using a Mac Pro mid 2010 with 32 Mb of RAM. Does anyone have a suggestion, is there a solution?



Photo of Michel DELFELD

Michel DELFELD

  • 247 Posts
  • 33 Reply Likes

Posted 9 months ago

  • 1
Photo of Marsha Levine

Marsha Levine

  • 29 Posts
  • 5 Reply Likes
Lightroom also slows drastically when I keywork (from a hierarchy) images in folders on my PC. I frequently have to close Lightroom down and restart it. When that no longer works I re-boot the machine. Very irritating.
Photo of Michel DELFELD

Michel DELFELD

  • 247 Posts
  • 33 Reply Likes
I must add that this catalog is having +/- 40.000 pictures
Photo of Robert Frost

Robert Frost

  • 406 Posts
  • 63 Reply Likes

Try deleting your LR prefs file and creating a new one.


Bob Frost

Photo of Michel DELFELD

Michel DELFELD

  • 247 Posts
  • 33 Reply Likes
Thanks to you Robert, but I did it already. It didn't gave enough speed up.

I made something else.

Until now, the catalog files were staying on one of my HDD dedicated for TIFF/JPEG images. This HDD is one this in direct connection with the computer (thus, it is constantly accessible).

I thought the problem I had was about swapping on this disk! I transferred the Catalog on the SSD System drive which has enough place.

Result is clear. LR goes at least ten times faster. But I hate placing data on system disk..... And the RAM decrease is much lower.

But the problem stays for other users that don't work with SSD. 
It's quite certain that smart collections are asking a lot of RAM work. If I compare the same picture about on a LR catalog without any smart collection, there no discussion the one with smart collections is the slower.

For me, the main advantage of LR catalog is about smart collection. (I don't a lot use the development section) Then considering the situation, I am afraid to say that LR doesn't make the job for what I am using it.

So, question: is there any application on Mac giving me satisfaction?
I already search a lot and din't got any effective solution
Photo of Robert Frost

Robert Frost

  • 406 Posts
  • 63 Reply Likes

I use 3 ssds on my Win10 computer. One for the system, one for the LR catalog and previews, and one for the LR acr cache files and a few other things like the PS scratch disk. Images are on a big internal HDD. It is quite fast but speeded up a bit when I renewed my prefs file. In hte past if I have had serious problems I have often deleted all the LR previews and the preview db files, and made new ones. That can often help if the previews get corrupted. I also clear the acr cache before making the new previews; that gets renewed as well.


Bob frost

(Edited)
Photo of Michel DELFELD

Michel DELFELD

  • 247 Posts
  • 33 Reply Likes
Thanks for the information. I am just now ordering a 2Tb SSD to replace a 4Tb that is not used a lot. My intention are to place FxPx and LR databases. Any way, I find this kind of slow down very bad, this mean to me that there is no correct refresh on the DB and on the Ram. 
Il already discussed that point with database specialist. they told me that the use of the LR DB is not the best one.