Skip to main content
Participating Frequently
March 6, 2012
Answered

Experiencing performance related issues in Lightroom 4.x

  • March 6, 2012
  • 188 replies
  • 629804 views

Anyone else notice that lightroom 4 is slow? Ligtroom 3 always ran fast on my system but Lightroom 4 seemlingly lags quite a bit.

My system is:

2.10 ghz Intel Core i3 Sandy Bridge

8 GB Ram

640 GB Hard Drive

Windows 7 Home Premium 64 Bit

Message title was edited by: Brett N

    This topic has been closed for replies.
    Correct answer Victoria Bampton LR Queen

    It's now impossible to see the wood for the trees in this whopping 43-page long thread.  Many of the original 4.0-4.2 performance issues have since been resolved, and it's impossible to figure out who is still having problems, and what they can try.

    I've started a nice clean thread to continue this discussion for 4.3 and later. http://forums.adobe.com/thread/1117506  Thanks to Bob_Peters for the suggestion.  I'm locking this one, otherwise it'll continue to get increasingly unweidly, but please feel free to continue existing discussions on the new thread.

    188 replies

    Participant
    March 29, 2012

    LR4 is un-beleivably slow on my system, which is very robust (mac pro, dual 3ghz 9 gigs ram). LR3 ran perfectly, just made the upgrade and it looks like I will be going back until they address these perfomance issues. At this point the new version is un-usable for me. Too bad

    Participant
    March 28, 2012

    +1

    Same here, dual or single screen doesn't matter. Performance is well below of what I got in LR3. Tried hints and tips, have a "virgin" LR4 installation now with catalog created from scratch, using DNG only, no improvement.

    Andreas

    Participating Frequently
    March 28, 2012

    I've read that Lr4 beta is actualy faster then the final thing?

    Just had to try it out myself and yes it is! Develop module is 50% faster...

    To prove again my point I did put a fresh Windows 7 on a SSD and without

    any other programs (not even Office) I intaled Lr4 final and imported the

    same photos from Lr4 Beta on my used and full of programs Windows 7...yet

    it was slower!

    So they did mess it up at some point after beta version!

    Marcelo Trad

    Participant
    March 28, 2012

    Hi All,

    I've exactly the same problems with LR4 performance as most of you (dual screen users).

    My hardware:

    AMD Phenom II X4 955 3.2 @ 3.8

    16GB of 1600MHz RAM

    HDD - WD20EARS couple of times ;-) (unfortunately not SSD)

    GIGABYTE GT240 1GB

    But there is one significant difference. As RAW (NEF) files from my D90 and D700 are rendering smoothly without any lags, RAWs from D70 (while working on dual screen ONLY) are just killing my CPU. I've 1-2s lag every 5s. It's horrible! And quite hard to explain. Any ideas maybe?

    Cheers,

    TR3znor

    Participating Frequently
    March 28, 2012

    Foregive me if this link has been posted here.

    For safety I will risk repetition:-

    http://feedback.photoshop.com/photoshop_family/topics/lightroom_4_update_from_the_team_update_scheduled_for_this_week

    Tony

    Participating Frequently
    March 28, 2012

    Just to throw in my own observations after having used the trial version for about 2.5 weeks now:

    The library module is fine. Once the previews have been generated, everything is snappy enough.

    Switching to the develop module usually takes a few seconds when it's the first time after starting up the software; but after that, it's a relatively smooth transition (although sometimes switching back to library module is a bit choppy).

    In the develop module, things are generally okay, except in the following conditions: (a) heavy use of the brush tool and (b) working on high ISO images (i.e. in the range of 3200). I haven't done too, too much with the brush tool in LR4 yet, but I can say that, very reproducibly, as soon as I start working on a high ISO image, the program comes to a crawl - it's virtually unusable, and would be absolutely unusable in a situation where high productivity is needed. When I say that it comes to a crawl, I mean switching from image to image in the develop module, using pretty much any slider, zooming in and out, applying sharpening/NR, applying lens correction, using curves, etc. As soon as I switch back to a low ISO image (400 or lower), it's all good again.

    In the case of all images (regardless of ISO), sharpening/NR are much, much slower than they were in LR3.6. In LR3.6, switching on and off the "details" (using the toggle switch) results in an almost instantaneous change. In the case of LR4, it generally takes a good 5 seconds or so for the effect to kick in (making it very difficult to judge the before and after).

    BTW, all this was done on a fresh catalog, created in LR4. However, LR3.6 is also installed on my system, and I did have the LR4 beta on there as well (but I uninstalled this before installing the full trial version).

    In terms of my system specs:

    i7-950 OC'ed to ~3.4GHz; 12GB RAM (rated 1600MHz; set at 1500MHz); AMD Radeon HD6870; LR catalog and photos on caviar black 1TB; cache on a separate black caviar 1TB; LR itself installed on my C drive, which is a Vertex 2 120GB SSD; running two, sometimes three monitors (but LR only running on one, i.e. not using second or third monitor); Win7 x64

    Camera specs: Canon 7D, using RAW files

    To be fair, another thing to point out is that it's not as if LR3 was always problem-free for me. Especially in earlier versions, it had it's slow moments (this problem seems to have improved in more recent version of LR3); but not nearly as bad as LR4 is.

    Hope this helps in terms of solving this issue, which is very significant for some.

    Participating Frequently
    March 30, 2012

    Just tried LR4.1RC. No improvement. Not even a slight one.

    Participating Frequently
    March 28, 2012

    Giant Company selling/charging user for it's beta software, user should have protection from this kind of transaction..

    tfitz100
    Participant
    March 28, 2012

    I'm wondering something. Do the users seeing 100% spike in CPU, who have multi-core/cpu systems see the spikes in ALL of those cores/cpus or a single core/cpu? I am now wondering if this is actually a process/thread scheduling problem that show's itself only under certain conditions in LR4.

    The reason I ask thiis is because I DO see a slowdown when I use the Adjustment brush with Tint (no idea why it's just this), but when this does happen, I see 1 single core spike and the rest are relatively idle, almost zero really. However, when I perform other functions, it appears that the other cores raise up slightly when I peform adjustments, but not 1 single core as in the adjustment brush case.

    I would be interested to see the results of what is happening to other users when they see the slowdown: What is happening in each core/cpu (depending on your system)?

    March 28, 2012

    My Core 2 extreme system with multiple cores spikes to almost 100%, hitting

    all cores.

    Sent from my iPhone

    Participating Frequently
    March 28, 2012

    gadgetgeek wrote:

    My Core 2 extreme system with multiple cores spikes to almost 100%, hitting

    all cores.

    BTW, taking 100% CPU is not by itself wrong or bad. In general you want all available CPU resources used to get the job done faster. If all cores are at 100% and it's still slow, that's bad. Alternatively if it's CPU-bound (not disk or I/O-bound), slow, yet all cores are *not* being used, that's bad. It indicates available CPU assets are not being used, typically because the app is poorly multi-threaded. In that case you often see a single CPU pegged, but an aggregate CPU meter averaging all cores shows a lower percentage. In general recent upper-echelon Adobe apps use multiple threads/cores pretty well, esp. Premiere Pro/Photoshop CS5 and later. I don't know what happened to LR4.

    Participating Frequently
    March 27, 2012

    I´m dealing with a lot of slowness and freeze up performance (if you could call it performance) in LR4...Just wonder: what are these guys doing over there at Adobe Labs? Too much Facebook for them maybe?

    Because I´m trying hard to work here and make a livin out of photography.

    Have said that, I have a Q6600 quad core with Nvidia GTX8800 +8gb ram and no antivirus or other program that would slow down my performance (just work computer only)...also have a raid 0 with two 7200rpm disks.

    Noticed that no matter if I put pictures on external e-sata disk and import and use it from there or on my hard drive, still slow.

    When I try to use with a Bamboo Connect.........just terrible!

    I felt like setting my whole table on fire after trying to edit a catalog with no more than 50 pictures on it...ajusts on the sliders are imprecise as they are so slow!

    I noticed a increase in my work hors more than 30% definately...

    Gave away my LR3 and I´m almoast calling Adobe and returning my LR4 and using LR3 until they come up with a solution...

    Maybe the price droped and quality of the programers also droped this time...

    Sorry Adobe, but I´m realy desapointed with this problems.

    Community Expert
    March 28, 2012

    When I try to use with a Bamboo Connect.........just terrible!

    Sounds like the tablet bugs are still there. A quick google reveals this: http://www.lightroomforums.net/showthread.php?14184-Wacom-Bamboo-Pen-problem

    I don't use one of these but Lightroom has a long history of really really badly interfering with drivers from wacom tablets. Some people can get this to work apparently but it is all very precarious. You often have to make absolutely sure you're running the very latest drivers for the tablet.

    Participating Frequently
    March 28, 2012

    Yeap!

    I´m running the latest drivers and of course the latest software...It´s

    just a pain.

    Other programs like Photoshop, Bridge, end even Capture One or Nikon

    Software does not lag at all with Wacom tablets.

    They actualy tend to guet better as new versions are released. Even Windows

    is getting faster...Vista was terrible, 7 is great, 8 seems to be even

    better and faster.

    I´m hoping they come outr with a solution to this Lr4 issues soon.

    Oh, I was editing a video footage on Lr4. Ok got to love this possability.

    I "saved" the metadata a couple of times (always do that to make sure) and

    deleated everything since I was moving the whole project to a new laptop

    computer. Surprise surprise...none of the cliping/rating/color tag came

    with it!

    Asked the question to Adobe and they said that Lr4 does not save metadata

    for video files.

    So let´s think about this: one of the Lr4 and Lr in general greatest

    features is the ability of doing this sort of thing, tag rate and so on.

    And you can see videos but canot do any taging.

    Thanks for leting us know ahead of time Adobe, you just could save me more

    than 12 hours of work.

    So I found a way of bypass this...just do your cliping and rating and save

    a catalog after just fot that job or the way you like better.

    Oh well I might sound like a complainer but I´m not...just had too many

    disapointment with Lr4 and need to let it out!

    =)

    Marcelo Trad

    March 27, 2012

    Just installed and tried photoshop cs6 beta. i tried the new adobe camaera raw with x64 bit and hey man, this thing is FAST. compared to lr4 adobe camera raw is nearly as twice so fast than lightroom. unbelievable. for now camera raw is my preferred raw engine. amazing. can not belive they use the same engine. happy now with adobe camera raw, still very sad about lightroom.

    chris!

    acresofgreen
    Inspiring
    March 26, 2012

    I was really looking forward to upgrading to LR 4 from LR 3, but this thread has convinced me to hold off for the time being or until I buy a new high-end computer, which won't be any time soon. 

    Bob Gates
    Participant
    March 26, 2012

    I just upgraded and found that when using a slider nothing happened until I clicked to enlarge the image, the the change kicked in.  I mean I could wait forever, just nothing happened.  I found the advice to export to a new catalogue, remove all previews and clear the cache and so far everything seems to be working ok.  On a fast Windows machine.