Forgotten in its old age

by Aditya

submit your photo


Hall of Fame
View past winners from this year

Please participate in Meta
and help us grow.

Take the 2-minute tour ×
Photography Stack Exchange is a question and answer site for professional, enthusiast and amateur photographers. It's 100% free, no registration required.

I'm running Lightroom 2.6 on Windows XP and it runs painfully slow. Just navigating from one image to the next takes a few seconds.

What can I do to speed it up?

share|improve this question
    
What cpu do you have (or cpu speed)? How much memory? What kind of video card? Hardware does play a role in your performance, but recommending improvements will require knowing what you currently have. ;) –  jrista Jul 24 '10 at 3:57
    
This one might be better on Superuser, since it's really about computer performance optimization. It's also kind of obsolete due to the software version asked about. –  mattdm Oct 29 '11 at 13:18

6 Answers 6

up vote 11 down vote accepted

Something that hasn't been mentioned yet: in 'Catalog Settings' turn off 'Automatically write changes into XMP'. This will prevent LR from automatically dumping its catalog metadata, keywords, rating, labels and develop settings back to your photo files. By doing so you will reduce the number of disk operations performed by LR. You can still write your metadata back manually, as I describe in this other question.

I have 8GB of RAM and I process 21MP RAW files out of a Canon 5DMII. Increasing disk performance is how I made it run faster. I replaced a pair of fairly zippy Hitachi SATA 15,000 RPM drives by a pair of 160GB Intel X25G2 SSD. Be careful with your choice of SSD drives, they are not born equal. Most of them read really fast, but many are slow on write. Pair your SSD with a modern operating system like Windows 7, one that supports the TRIM command.

What should you put on a SSD and what should you leave on a standard drive? Opinions differ, but here is what I would recommend:

  • your LR catalog file (Lightroom 3 Catalog.lrcat), which is where LR stores its metadata, keywords, rating, labels and develop settings
  • your Previews directory (Lightroom 3 Catalog Previews.lrdata), which is where LR stores intermediate representation of your photos for faster viewing (1:1, low res, thumbnails, etc)
  • your Adobe Camera RAW Cache (ACR Cache)
  • your RAW files, or at least a subset of them

What is the Camera RAW Cache? Quoting Jeff Schewe via Luminous Landscape Forum

Every time you open an image in Camera Raw the full resolution of the image must be loaded into Camera Raw… as you can imagine, this can be pretty processor intensive… the Camera Raw cache will cache recently opened images to make re-opening them faster. There’s a preference limit to determine the size and the cache will remain constant in size by flushing out older cache files when newer images are loaded into Camera Raw.

You can change the default location of your catalog, previews and Camera RAW Cache from the Preferences and group them on the same SSD. I would definitely recommend increasing the size of your ACR Cache, if you can afford it.

RAW files are big. You don't need to have all of them on a SSD, but what about the past 6 months worth of photos? Move older photos back to a standard drive every month or so (do it from LR of course).

Do you need to put LR or the whole Operating System on a SSD? If you can, sure, it will start faster and feel a bit more responsive, but I don't think it's critical. If you don't have a lot of RAM though, try to put your page file and TEMP directories on the SSD.

Should you go RAID0? I really recommend against it, unless you have really strong backup habits and monitor your RAID controller regularly. Remember, RAID0 uses 2 drives: if one dies, you lose the data on both. Don't risk it. I personally like RAID1 a lot for this very reason and from past experience.

Finally, you will "feel" LR run faster if you let it generate your 1:1 photo previews during import. I usually do something else during import anyway, run some errands or whatnot. In any case LR has to generate your 1:1 previews sooner or later when you go to the Develop module, right? So you might as well let this happen during import.

share|improve this answer
    
Excellent answer, this should easily be voted up as the best answer. Even after all of that, I still with lightroom was faster. It really isn't as fast as I would like for culling images and rating. –  dpollitt Jun 16 '11 at 16:22

Upgrading to Lightroom 3.2 is cheap and easy. You'll find version 3 a lot more responsive than 2.6, and version 3.2 even more so. In most situations where Lightroom 2 makes you wait, Lightroom 3 will do its processing in the background, so you can continue to interact with the program.

You didn't say what hardware you're running, but if you're using Windows XP, it's probably an older system. Lightroom really taxes PC hardware. Getting the fastest PC you can afford is definitely a good idea. I'd recommend a 64-bit system with lots of RAM and an SSD drive. If you can't afford an SSD big enough to store your images, use an SSD for the operating system and your Lightroom catalogs, and a normal hard disk to store your RAW files.

Lightroom doesn't benefit from multi-core CPUs as much as I'd like. If you tend to have Lightroom run multiple background tasks (import, export, render previews) as the same time, your computer will stay more responsive with a quad core CPU. If you don't run multiple background tasks, then a dual core may be a better choice. For the same money, the individual cores on a dual core CPU are faster than those on a quad core.

Lightroom does not make use of GPU acceleration at all. So don't spend money on a graphics card unless you need it for other purposes.

share|improve this answer

Without knowing the amount of RAM or processor speed, it's hard to make specific recommendations, but Lightroom will perform significantly better with more RAM and a faster processor.

It also doesn't hurt to occasionally optimize the Lightroom catalog, which helps increase the efficiency of operations. On a PC it's under Edit->Catalog Settings, on a Mac It's under Lightroom->Catalog Settings. Click the "Relaunch and Optimize" button. Lightroom will do just that. It can take a while depending on the size of your catalog.

share|improve this answer
1  
To optimize in Lightroom 3 on the Mac, go to File > Optimize Catalog. –  Jon Freeland Jul 30 '10 at 2:21

Don't let the catalogue grow too large.

Separating your pictures into several catalogues can bring a lot of speed.

For me the main waiting point is waiting for Lightroom to render the 1:1 previews - if I let Lightroom render those on import I can usually work faster.

Of course putting the catalogue on a fast hard disk (SSD) helps, too.

share|improve this answer

Upgrade. LR 3 is a fair amount faster for me. I also have found that RAM seems to matter more than raw processor speed, at least for me.

share|improve this answer
1  
Personally I've found that Lightroom 3 is slower and uses more system memory to do the same job as Lightroom 2.x. The slower processing time is apparently due to the improved processing algorithms. –  Craig Nicholson Jul 23 '10 at 12:16

I'm not sure how well Lightroom performs when your catalog grows too large. I'd recommend improving general system performance by addressing the following areas:

  • faster & more system memory (limited by the 32-bit XP in this case but max out at 3GB if you can)
  • faster disk (at least 7200 RPM spindle, striped as RAID-0 or RAID-1+0 if you can afford it)
  • faster processor (the more cores the merrier, Lightroom might not make use of them directly, but the system is a multi-tasking OS and will make use of them nonetheless)
  • upgrade to Windows 7 (huge improvements in I/O (memory & disk) as well as processor core usage)

In terms of Lightroom itself, I can only suggest creating smaller catalogs.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.