Skip to main content
_
_delpk_
Inspiring
February 21, 2023
Answered

Moving the installation (Desktop) - Tips/Pitfalls

  • February 21, 2023
  • 4 replies
  • 3271 views

I used Lightroom Classic and I'm getting a new drive (a much faster one). So I intend to move the installation of Lightroom classic to the new drive (currently when using Lightroom it maxes out the existing drives output and it's getting a bit frustrating).

So before I attempt this I want to know what may go wrong, things not to do etc. So my photos will all stay in the same location, the current drive still works, so how best to approach this task?

 

My thinking is to get lightroom to store it's catalog on exit -> uninstall -> reinstall in new location -> point it to the catalog it saved on the previous exit -> all will be happy!  

This sounds simplistic (hoping it is), but am I missing anything. Will it break all links, modifications of images etc or will it just work?

This topic has been closed for replies.
Correct answer dj_paige

Thanks. The associated previews, are they linked to the catalog or the cache. I expected they were part of the cache. In which case the cache is on a faster drive. But when monitoring disk activity that faster drive is still not being accessed much while using LrC.
I'm going to move the catalog next and see what gains that gives. 


Move the catalog and the previews (folder whose name ends with ... previews.lrdata) and the masking data (folder whose name ends with lrcat-data) together.

 

I don't think the cache is used by the Library Module (although you still need to confirm you are talking about the Library Module)

4 replies

_
_delpk_Author
Inspiring
February 21, 2023

There are some great and very usful comments in this thread. I've now got a system that is perfoming much much faster. So I thought I'd sum up what was the start, what happened and changed. Hopefully this may help someone else.

I have 2 SSD's and 1 HDD.
Windows is on one of the SSD's - lets say C:  (M2 storage)
E: is a small SSD (0.5TB) so I didn't put LrC (or any other Adobe product) on it.

F: is a HDD that's fairly large. This stores all my photos and I also have LrC installed there - as well as the cache, backup, preferences - everything as far as Adobe is concerned.

The machine has 16GB of Ram - Win 10.

The LrC cache was increased to 20GB and I did other things such as 'Optimize Catalog', turn off 'generate previews in parallel'. But when scrolling through lots of photos in Library mode, the disk (F:) was the bottleneck. It couldn't read/write fast enough as the CPU and graphics card were barely getting up to speed.

I moved some of my raw photos (the ones I was wishing to edit/select) onto the small SSD (E:). No improvement in speed.
I moved the cache onto the E:, again no improvement in speed.  F: was still being hammered.
I then followed @Jim Wilde advise on how to move the lightroom installation (which was my orig Q) - again no speed improvement. 
Lastly I moved the whole catalog to the E: (small SSD) and it is now much faster. Monitoring resources, and now the CPU/GPU are actually being used!  

So my raw files are still on a slower HDD, which is a minor slowdown, but it will do until I get the new larger SDD and I can move them onto that.

(just for reference I use Backblaze to back up everything on my machine, which on inital import of files will slow the system down a little. Used to use local NAS but Backblaze is now cheaper and simpler to use)

 

Thanks again!

dj_paige
dj_paige
Legend
February 22, 2023

So my raw files are still on a slower HDD, which is a minor slowdown, but it will do until I get the new larger SDD and I can move them onto that.

 

As earlier in this thread, @_delpk_ , you talk about the need for speed, but you don't tell us what is slow. There's really only a trivial benefit, so small you probably won't notice, to getting a faster disk for your photos — as stated by @Jim Wilde. So please tell us what speed problems you are having — state exactly and in detail, what actions are slow?

_
_delpk_Author
Inspiring
February 22, 2023

Are you loading in "Loupe" view?

 

What size previews do you generate at import? Was the test you ran using 1:1 previews that had previously been generated? 

 

This slowdown does not sound like something that a faster disk would help with. The generation of a non-fuzzy preview is done by the CPU, that's where the slowdown likely is.


This was in a recently viewed folder, so there should have been a cached/generated/preview image available.
That test I did was in Loupe view.

In the interest of another test, I tried the Survey view and it barely touched the disk with raw files.

And at the same time I went through 60 photos in roughly 45-50 seconds. So I think I've found a winning view for selecting images. Guess that's why it's called Survey view.
CPU didn't get higher than 40% (most of the time 20%).

I also did the Loupe view test again and each time I could visibly see it loading you can see the disk activity spike.

GoldingD
GoldingD
Legend
February 21, 2023

Some comments pertaining to performance of LrC

 

  • Lightroom application location. Must be on a physical drive, typically on C drive (Windows), no performance advantage to be on a fast drive.
  • Windows C drive. If running out of room, check for junk, check for a recycle bin not flushed, check for temp files not flushed. Move documents to other drives.
  • Catalog location. Must be on a physical drive, internal or external. Placing the catalog on the fastest drive can help performance. The drive must have at least 25% free space (in percent) , some say 20%. 
  • Library previews must be on the same drive as the catalog, within the same folder structure. Just leave it alone.
  • When working in the Library module, the Camera RAW CACHE is not used.The Library previews are used. 
  • Photos can be on any drive, preferably internal or external, preferably not server, NAS, or Cloud. Their is no advantage via fast  hard drives.
  • When working in the Develop module, the Camera RAW CACHE is used. The filmstrip, the Navigator, use Library previews.
  • The Camera RAW CACHE can be on any drive, internal or external. not a server, NAS, or Cloud. It can take advantage of being on a fast hard drive. 
  • On a Windows computer, placing the Camera RAW CACHE on the C drive can cause performance issues. Problem is competition with the Windows Paging file typically on the C drive.
  • Lrc can take advantage of a larger Camera RAW CACHE, many users accept the default 5GB value, that is way too small.
  • Backups of the catalog, and backups of the photos (these are separate) should not be on the same drive as the originals. They should be on separate drives, internal, external server, NAS or cloud. Probably not on C drive as C drive is often in use and as such a vulnerable resource. You should maintain at least two sets located on different media. One local in case of drive failure, one external and locked up in case of theft, for additional safety one external or cloud sent or located far away in case of natural disaster (typically for business safety)
  • Windows Paging file, hmmm??
    dj_paige
    dj_paige
    Legend
    February 21, 2023

    So I intend to move the installation of Lightroom classic to the new drive (currently when using Lightroom it maxes out the existing drives output and it's getting a bit frustrating).

     

    It's not clear if you are talking about the photo files, the catalog files, the progam itself, or all of the above. So please tell us which of those you are talking about.

     

    I also point out that depending on exactly what actions in LrC are slow (which you don't tell us), a faster drive may not fix the problem. So please tell us, and provide details: what actions in LrC are slow?

    R
    Community Expert
    richardplondonCommunity Expert
    Community Expert
    February 21, 2023

    I guess the fuller question is, what actions in LrC are currently slow that would not improve by transferring the ACR Cache, and the Catalog with its accompanying folders, onto faster performing storage? 

     

    I would expect the LrC application is entirely operating in RAM once started up - assuming there is enough RAM present. If there is not enough RAM, then it will be the OS paging memory to disk which then limits things AFAICT, and that will not change by moving the application install. Another common bottleneck is CPU (main processor) - also not improved by moving the application install. Same thing for GPU (graphics co-processor).  

    Jim Wilde
    Community Expert
    Jim WildeCommunity Expert
    Community Expert
    February 21, 2023

    No, that's not the best way to move the catalog. Do it using the instructions in this post: https://www.lightroomqueen.com/find-move-rename-catalog/

    _
    _delpk_Author
    Inspiring
    February 21, 2023

    Thanks but that's not quite my question. I'm not wanting to move the catalog. I wish to move the installation of Lightroom. I have multiple drives and moving the photos is simple enough inside of Lightroom (I've done that before).
    I've moved the cache to a faster drive as well as the sync'd images. But as soon as I use lightroom classic the usage of my drive that has the installation of Lightroom maxes out. Hence the reason I wish to move the installation.

    I may well move the catalog as well, but until I get my new faster drive, the other fast drive I have isn't massive. So only moving chunks at a time to slowly improve speed.
    Thanks for the tip so far.

    Jim Wilde
    Community Expert
    Jim WildeCommunity Expert
    Community Expert
    February 21, 2023

    To install on a different drive, you need to use the Creative Cloud desktop app>Preferences>Apps tab>Change the install location. Then uninstall and re-install. On restart LrC will automatically open the previous catalog. 

     

    What does "the usage of my drive that has the installation of Lightroom maxes out" actually mean? 

      Terms & ConditionsAccessibility statement
      Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices