Skip to main content
Adobe Photoshop Family

16 Messages

 • 

2.1K Points

Mon, Jun 18, 2012 4:43 PM

Lightroom: Performance and optimization: LR is slow

LR 4 is excruciatingly slow. Until Adobe is able to do something about this I am recommending my students and readers continue to use LR 3 or switch to Aperture.

Responses

4 Messages

 • 

84 Points

8 years ago

I have installed 4.1 and have since optimized my primary catalog.

I am having tangible, measurable speed issues.

System specs:
Processor Intel(R) Core(TM) i7 CPU X 980 @ 3.33GHz
Memory (RAM) 12.00 GB
Graphics NVIDIA GeForce GTX 460
Gaming graphics 4096 MB Total available graphics memory
SSD Primary hard disk 22GB Free (112GB Total)
+ 112GB PCIe SSD for 'working catalog' LR files (I use the term 'working' loosely in this scenario).

Images in RAW average size: 16MB
Average catalog size: 200 images

Exact operations and elapsed times:
Opening Lightroom (from clicking on Icon to LR4 flash screen leaving view): 13.3 secs.
Moving between sequential images in library mode: 1.7 secs
Moving between sequential images in Develop mode: 1.9 secs
However If i move between images quickly i.e tap right arrow 10 times in a row, LR becomes unresponsive and can take up to 30 secs. (I know it is unresponsive because I have the resource monitor open simultaneously).

Things get worse as I move sliders in develop mode, or heaven forbid, I invoke the wrath of a preset. Lightroom becomes unresponsive and it can take minutes, these are not detailed presets; I have detailed presets and I might as well go make a coffee if I dare to use these on a single image (I haven't dared batch processing as I'm not sure I'd like how I look with a beard.

Humor has been used in this post, but the pain (and unresponsive nature of LR4.1) is very very real.

My Lightroom 4.1 goes unresponsive (resource monitor states this) too many times to count whilst developing.

I have read (or felt like I have read) every post and tried every trick to get the performance that everyone else seems to have.

My hat goes off to Steve Anchell for taking up the cause and fighting for those of us that are unhappy with the performance of a 'stable' build.

I am very happy for all of you that don't have problems with LR, but I don't need to hear that, I need to hear that adobe has at least acknowledged that they are aware that some of us out there have this issue, that this is an issue and are working on a solution, that in itself may be enough for me for now.

4.5K Messages

 • 

76.3K Points

Adobe has acknowledged the problem, but I doubt they will do it repeatedly, in each new thread about it...:

http://feedback.photoshop.com/photosh...

Fingers crossed that Lr4.2 will remedy for even more people than 4.1 did.

4 Messages

 • 

84 Points

Hi Rob,
I originally thought that was the case, however quoting Rikk Flohr in an earlier post in this thread, referencing the post you have linked:

"The post to which many of you refer and hold up as evidence: http://forums.adobe.com/thread/971581... is 863 posts long. It began on March 6th-just over three months ago. Lightroom 4.1 was released on May 29th ( three weeks ago roughly) The announcement was made on post 804. 93% of the posts in this thread refers to a previous version of Lightroom."

Rikk is implying that the issue that adobe acknowledged was prior to 4.1's release and therefore relates to a previous version of Lightroom (4.0) if this is the case (and apologies Rikk if I have misrepresented) the issues I am having post 4.1 are not 'acknowledged'

4.5K Messages

 • 

76.3K Points

Hi Alexander. If it's any consolation, I too think Adobe should attend more to their users, on these forums. Often, a simple "we hear ya, and we're working on it" every now and then, can go a long way. I have no idea why they don't do it more often. I'm pretty sure it's not that they don't know, nor that they don't care, and I'm pretty sure they're working on it... I have no inside knowledge one way or the other, but I've been around long enough to know they are likely to come up with a version that fixes many but not all of these problems. Probably they already have as much info as they can handle, have stopped reading these forums for such, and are busy working away..., or so I imagine.

4 Messages

 • 

84 Points

Hi Rob, Thanks.

However the thread you referenced commenced 3 months ago prior to 4.1's release, I can only assume the 'acknowledged' related to the issues prior to 4.1. It's a pity the same thread has been used for post 4.1 issues so we, users, can not be certain if our issues have been acknowledged.

This thread was commenced post 4.1's release (1 day ago) and I feel justified (as I'm sure all those who have issues with 4.1 feel) in seeking an acknowledgement to this thread.

Alternatively (or additionally) if anyone wants to offer me constructive feedback or support on this support forum I'd be happy to receive it.

4.5K Messages

 • 

76.3K Points

Fair enough. I already gave my best advice above ^ .

10 Messages

 • 

156 Points

8 years ago

I would like to add measurable evidence:

Intel i7-2720QM
Nvidia NVS4200M 512MB
8 GB RAM
SSD
LR4.1
optimized catalog
all new drivers

I tell LR to create standard size previews for some 1500 24 MP photos. (Sony A900 or Nex7)
At the beginning (around image 50) it only takes 2-3 seconds for one preview to be generated. Once I reach image 500, I am up to 20 seconds - and things get worse from there.
Also scrolling in grid view is relatively smooth after a fresh start of LR, but after an hour of preview generation is super laggy and even freezes at times entirely.
During all this a maximum of 16 % of my CPU is being used and only 1 GB of my 8GB RAM.

a) this is unacceptable.
b) Why does LR not use more of my resources, especially more CPU? Seems like this could help.

47 Messages

 • 

836 Points

8 years ago

LR4.1 is Still slow...Help Adobe please!

10 Messages

 • 

166 Points

8 years ago

I to would like to contribute measurable evidence in the hope that Adobe will provide us with a solution.

Mac OSX 10.6.8, MacPro 2 x 2.8 Quad-core Xeon, 16Gb RAM, ATI Radeon HD 5770 card, dual monitors (NEC 2690 & Dell U2312HM.)

Files are a mixture of 5D mk1 and mk2 RAWs, single LR4.1 catalogue has ~15,000 images.

My specific issue is with the Develop module.

With LR 3.6, all sliders moved with no jerkiness or hesitation, the screens updated immediately in real time etc etc. In short, perfect, no issues. (BTW - my 3.6 catalogue has close to 100,000 images in it!)

Using the Develop module in 4.1, there is a 5 - 10 second delay when switching between images. 1:1 zoom takes 3 - 7 seconds. Moving sliders has a lag of 5 - 12 seconds before the slider moves, then a further 4 - 8 seconds before the screen updates with the adjustment. Crop tool takes 10 -15 seconds to become active after clicking the icon.

I have tried all suggested workarounds (cache/history clears, integrity checks, re-build previews etc etc.) to no avail.....and I really shouldn't have to, should I? When I buy a product, it should work out of the box!!

If anyone from Adobe requires any further information, please tell me exactly what data you need and I will happily supply it.

I want to use LR4.1; the new Raw engine alone gives markedly improved results over 3.6.

However, I am a busy full-time working pro photographer. In its current form LR4.1 is not fit for purpose. TK Anthony's earlier post illustrates perfectly why.

Adobe have done some good work in rectifying the initial glitches (which, whatever anyone says, really shouldn't have crept through internal testing!) in terms of import speed, web gallery build etc.

However, the issues with the Develop module have been there since day 1 and have not been addressed. The web is littered with complaints about this specific issue; it is not "just a few isolated cases"!

Adobe, please acknowledge this as a major issue and at least give us a timeline for when a solution will appear!

Until then, I will switch back to LR3.6.

441 Messages

 • 

6.6K Points

8 years ago

What happens if you use 2010 process mode in LR4.1. Do you still get the problems, or does it behave like 3.6?

Bob Frost

10 Messages

 • 

166 Points

8 years ago

Bob, yes, this does seem to help a little, but still does not bring the big catalogue up to 3.6 levels of speed. Also, I really want to use the 2012 option. :-)

Now, since my last post, I tried a small test on a single set of files. I took 1,005 CR2 RAWs, created a brand new catalogue, asked to delete and then re-render 1:1 previews (my 1:1s are high quality 2048 pixels.)

This route makes a huge difference - LR4.1 is now as slick as 3.6 on this small catalogue. Hmmm....and this was with 2012 option.

Nothing else has been changed. Now, I've done this before, and it made no difference. However, that was on a sub-set of files in my main catalogue, not the full monty.

I will try to test on my main catalogue with fully re-built previews over the w/e but am pushed for free time.

HTH and watch this space......

JB

2 Messages

 • 

92 Points

8 years ago

I'm now using LR4.1 with PV2010 to get the speed that resembles LR3.6. LR4.1 using PV2012 is as described by many users in this thread - too slow for use when one needs to process a few thousand images. I thought I had my workflow down pat when using LR3.6 and was very excited about what 4.1 would offer. To say I'm disappointed might be understating it a bit. I'm interested to hear what progress Jonathan makes.

Flash

946 Messages

 • 

13.8K Points

"LR4.1 using PV2012 is as described by many users in this thread - too slow for use when one needs to process a few thousand images."

I do it all the time, but....

http://forums.adobe.com/message/44503...

10 Messages

 • 

166 Points

8 years ago

Right - not good news.

I kicked off a full rebuild of the previews on my main work in progress catalogue at 7am yesterday morning. This catalogue contains 15,014 files, 99% of which are Canon 5D and 5D mk2 RAW files, with a smattering of PSDs and JPEGs.

As at ~7pm last night (12 hours after the process started!) LR4 had reached file 8,000...! 12 hours to build 8,000 previews? Holy cow, that's dreadful!

So, left machine running overnight and sometime in the wee small hours (sorry, can't say when; I have to sleep and have a life to live) the process finished.

Now this is not good ; ~24hrs to build 15,000 previews is appalling. However, the rebuild threw up a strange message I've never seen before.

A screen had popped up (presumably when the process had finished) telling me that LR could not build previews for a set of around 600 files, 'cos it couldn't find them. Fair enough. The problem is that the set of files LR was looking for are not in this catalogue, and never have been. Doh! :-(

This catalogue was created when I first installed LR4, and was created directly from my existing LR3 catalogue. This set of files HAD existed in the LR3 catalogue, but had been removed BEFORE I converted the LR3 catalogue to LR4. "Curiouser & curiouser" said Alice!

So I'm suspecting the LR4 catalogue is corrupted in some way, despite having cleared caches and run integrity checks before starting the preview build.

So, I'm going to create a brand new catalogue and import all the folders and files in the current catalogue, to see if this makes a difference to the preview build speed.

Sadly, the rebuild has failed to speed things up noticeably; sliders are still 'sticky' switching between files takes several seconds, etc etc. This is the same between PV 2010 and 2012; 2010 is a wee bit quicker, but still unusable for day to day work.

I ran Apple's Activity Monitor during the build. I'm not a techie, so can't interpret these stats, but if they tell anyone out there something, I'd love to hear it! :-)

%CPU was anywhere from 300 - 600%.
There were 24 - 36 threads in use.
LR was using between 1.3Gb and 1.8Gb of Real Memory.
System Memory showed 10Gb free, 0.75Gb Wired, 2.46Gb Active and 1.79 Gb Inactive.

So, kicking off the new catalogue now.....watch this space.....! :-)

441 Messages

 • 

6.6K Points

8 years ago

Instead of importing the files afresh (which will lose your history, and edits if you haven't got xmps), export the catalog to a new one without previews. I did the same when upgrading from LR3 and that left behind a lot of old stuff that was upsetting LR4. You don't lose history or edits in an export to new catalog.

Bob frost

441 Messages

 • 

6.6K Points

8 years ago

As for re-rendering previews, my 65K of nefs takes about 3 days and nights to render 1:1s on a fairly new fast desktop (6 core SandyBridgeE, with 16GB ram and SSDs).

I don't know much about Macs, but someone said your MacPro is getting a bit old! I do know that even on my quite new machine, rendering D800 36MP nefs takes about 4 seconds each, so that is about 1000 nefs per hour.

My old D100 nefs were only 10MB each, compared with the 40 MB of my D800 nefs (compressed).

I think we are just seeing the effect of wanting to do more complicated processing on bigger and bigger files.

Bob Frost

441 Messages

 • 

6.6K Points

8 years ago

Just found this post on the other LR forum:

"I rember back in the days of LR2 on my 2006 MP 1:1 previews took on the order of 3-5 seconds. With each version of LR since then, this got longer and longer, until LR 4.0 streatched it to 10+ seconds. LR 4.1 cut a couple seconds off, but working in LR was still more a chore than something I look forward to as I did 3 years ago. Last week I bought a new 5,1 Mac Pro (yes I know, the processor is 3 years old). It's the 6-core model (3.33 GHz) with 24 GB of RAM and a 512 GB Crucial SSD, to which I moved my LR master cataloge. I'm happy to report that. $3600 later. I'm zipping through 1:1 previoew in 2-3 seconds, even in Develop mode."

[http://forums.adobe.com/message/45163...]

Bob Frost

3 Messages

 • 

82 Points

8 years ago

Peter Orford
Have used LR since it's inception version 4.1 is too slow for me so I won't buy it till there is a marked improvement .

Have tried all sorts of work a rounds not worth the time and effort .

Its a shame as is was a good product .

Peter Orford

10 Messages

 • 

166 Points

8 years ago

Bob, many thanks for your input ideas. Hadn't considered exporting the catalogue w/o previews - good thought! :-)

Glad my machine is as responsive as others. ;-)

It is 3-4 years old, but still well above Adobe's min spec for LR....WELL above. Guess you're right - bigger files, more intensive tasks etc. I normally import a max of 1k - 1.5k files at a time, so haven't really explored preview build times in depth before.

That ain't my problem; my problem is still LR4 being unusable on large day to day tasks. :-(

Sadly, I have to return to the 'real world' for now, and process work for clients.

I'll continue to follow this thread and also the one you highlighted on the Adobe forums board. If I get a chance, I will run more tests and post back results as and when I can.

19 Messages

 • 

244 Points

8 years ago

Hi Steve, thanks for starting this thread. I have also been on one of the other threads about LR4 (http://feedback.photoshop.com/photosh...) and am having all the same trouble. I am sorry that you are getting some not so helpful pushback from some posters.
Here are some details from my situation:
I am using three different machines. All Macs. All running OS X 10.7.4 and LR4.1
MacBook Pro 2.4ghz Core2Duo 8gb ram
iMac 27 2.8ghz Core i7 8gb ram
iMac 27 3.06ghz Core2Duo 8gb ram

Here is the basic problem: generally LR3.6 was responding in "real-time" regardless of the operation. By real-time I mean that a change was visible as a Develop slider was moved, or an effect was visible as a brush was applied to an area. In LR4, at default settings the delay is often 5 or 10 seconds. another issue is when switching from Develop back to the Grid view in Library the delay is commonly 20-45 seconds.

But there is a very important caveat here that appears to be true for many, many Users: if you select PV2010, Do Not use the Noise Reduction AT ALL, and hide the filmstrip, the performance is noticeably better. There are still lags, but they are only a few seconds so it is somewhat acceptable for small editing sessions. However, PV2012 and the NR functions are two of the big features of LR4 - so what is the point of using it like that? That is basically LR3.6 with Blurb Books and poor performance.

I am a Pro Photographer and a single project easily has 1500 images that my first task is to quickly sort through making select/reject decisions and LR4.1 is slower than LR3.6 for even that basic task. I've been using LR since its initial beta and it has always performed well (although it has been less impressive with each version). Unfortunately Aperture is as bad, or worse, in my experience and I used Aperture 1, 2, and 3 and, while I have always preferred it's UI and management concept, it has always been a poor performer for me. That situation is so odd, too, because, like this situation with LR, many people claim to have exemplary performance while others say it is a dog.

The whole situation is terribly frustrating.

946 Messages

 • 

13.8K Points

Greg, there's a bug in PV2012 with Clarity and Noise Reduction. If you keep both of those off, does this fix the problems on 4.1 and PV2012 with slider response?

19 Messages

 • 

244 Points

Hi Lee, its better, as I mention above. Better, yet again, if I do not use PV2012 at all. One workaround I have been using (because I foolishly started a now 8500+ image project in LR4) is to paste lens profile settings, Clarity, Noise Reduction to a group of images once all other adjustments have been made and just before export. Problem, in this case is I have no ability to fine tune the NR or Clarity. I just apply based on same lens used/ISO/scene.

4.5K Messages

 • 

76.3K Points

You can fine tune using quick-develop (relative adjustment), no?

For finer control or relative presets, cookmarks:

http://www.robcole.com/Rob/ProductsAn...

946 Messages

 • 

13.8K Points

Okay, did you try the 1:4/1:8 etc. trick I posted above? That's a 4x increase in Develop slider performance.

6 Messages

 • 

136 Points

8 years ago

Is anyone here also having issues with extended delays (10-30 seconds) when deleting images from the catalog?

4.5K Messages

 • 

76.3K Points

No. But empty your recycle bin if you haven't done it recently.

I doubt that will yield sufficient improvement though. Consider deleting ACR cache, and export your catalog without previews to new catalog, then rebuild previews. - may help shake out catalog anomalies...

do you have same problem deleting images from newly created catalog? If so forget what I said before, it's something else...

6 Messages

 • 

136 Points

Thank you for the reply....

My issues with 4.1 are listed below (I did not have these issues with 3.6 or 4.0, although 4.0 was noticeably slower for me than 3.6):

Slow launch (sometimes hangs forever and I have to delete the pref file)
Delay moving between Library and Develop
Delay deleting files
Delay building 1:1's.

My system:
i7 2600k Sandy Bridge (not overclocked)
Win7 pro
32gb ram
Sata III SSD for apps
Catalog, previews, and images are on 7200rpm internal drive
I'll be picking up another SSD for the catalog and previews, but I don't think that is my main issue, as these issues were not present prior to the 4.1 update.

This morning I deleted my 1:1 previews, and selected a folder with 1600 images to generate 1:1 previews. After 7 hours, it had generated 1083, so roughly 23+ seconds each.

I have deleted my ACR cache. I have also done the preferences file "fix" that was suggested in another thread, and intermittently need to trash the pref file. I have tried setting LR priority to high and core affinity to 0,2,4.

My next steps will be to try a newly created catalog, and if that improves matters, I'll export to a new catalog without previews. If that does not work, I'll probably go back to a Bridge/CS5 workflow. I can't waste anymore time on this.

6 Messages

 • 

136 Points

Forget to mention, the 1600 images are 5dII or 7D RAW files.

4.5K Messages

 • 

76.3K Points

Yeah Dave, something not right. If I were having these problems, I'd be tempted to switch to Plan B (or C...) too, until Adobe gets their Lr ship together.

Lightroom is slow to launch for me too, but then I have 30 or 40 plugins all starting simultaneously and competing for catalog access... but it *never* hangs on startup. Something is wonky right from the get-go in your case.

In a nutshell, problems are usually:
* Lr files (e.g. cache, previews, prefs, catalog, plugins, presets, ... ), or
* System: e.g. drivers, permissions, file-system, background services, ...
or both.

Hoping for improvement,
Rob

6 Messages

 • 

136 Points

**UPDATE** - My issues were not the fault of LR4.1. It seems my issues were hard drive related, which also explains the odd issue of hanging deletes. I have been getting drive errors for the last 2-3 weeks, and it seems the drive's file structure is corrupt, or the drive is slowly crashing. Checkdisk errors out. I exported the catalog to an external drive and everything is useable again.