Skip navigation
This discussion is locked

Experiencing performance related issues in Lightroom 4.x

Aug 6, 2012 3:58 PM

  Latest reply: Victoria Bampton, Dec 18, 2012 11:37 AM
Replies 1 ... 13 14 15 16 17 ... 43 Previous Next
  • Currently Being Moderated
    May 2, 2012 11:50 AM   in reply to Malco48

    It's not random; there is a pattern and it's widespread.

     

    I'm going back to 3.6 for now...I can't take it.

     
    |
    Mark as:
  • Currently Being Moderated
    May 2, 2012 11:59 AM   in reply to rpavich1234

    This is pathetic.

     

    I uninstalled LR4 and reinstalled LR3 and it's LIGHT GREASED LIGHTNING compared to LR4...no pauses, no waiting....faster than crap. I didn't realized how messed up LR4 was until I just went back and compared.

     

    Until this is cleared up...I'm sticking with LR3.

     
    |
    Mark as:
  • Currently Being Moderated
    May 2, 2012 12:49 PM   in reply to BCormier

    Hate to go aginst the grain but strangely for me it has speeded up with Lr4.1RC2 and I am using a 3 year old top spec macbookpro!!! (2.66ghz 8gb sdram, 7200rpm hard-drive)

     
    |
    Mark as:
  • Currently Being Moderated
    May 2, 2012 10:47 PM   in reply to BCormier

    I'm using LR RC2, and while it's not horrible, I'm finding that after a while using it the sliders get so laggy you can't fine tune accurately, and eventually it grinds to a halt almost completely.  A restart of LR fixes it, so I'm quitting LR every thirty minutes or so to avoid issues.

    Model Name: iMac

          Model Identifier: iMac9,1

          Processor Name: Intel Core 2 Duo

          Processor Speed: 2.93 GHz

          Memory: 8 GB

    System Version: Mac OS X 10.6.8

     

    I don't remember the beta being this bad, but I haven't used LR 4.0 or RC1 to compare.

     
    |
    Mark as:
  • Currently Being Moderated
    May 3, 2012 3:50 AM   in reply to Susan S.

    Even RC2 is much slower than the ligtning fast LR3.6 ..Nothing is more frustrating than moving a slider and the result happens 3 seconds after you stop.  .. I think I'll be uninstalling Lr4 until I see that it's fixed. I'm sure it will happen.... but I'm not waiting and dealing with this .Toggling from Lightroom to photoshop has a 45 second load time  ...Really ???   .. I bought the upgrade and have a serial number for downloading it in the future.. untill then ..I'll go back to my 3.6 which I used on a daily basis and was VERY content with ..

     

    System :

     

    Windows 7 home premium

     

    Intel Quad Core i7 2600  3.40 GHz

     

    Nvidia 405

     

    12 GB ram

     
    |
    Mark as:
  • Currently Being Moderated
    May 3, 2012 7:57 AM   in reply to Madscape

    Just a comment...  this is a general forum for LR.  All these comments

    are great..   but I would suggest you post them to the bug and feed back

    page.  Not sure how much time ADOBE spend monitoring this public forum.

     

    http://feedback.photoshop.com/photoshop_family

     
    |
    Mark as:
  • Currently Being Moderated
    May 3, 2012 9:39 AM   in reply to LR_Mowang

    Oh, they should monitor this, the header says: Lightroom 4 is slow

     
    |
    Mark as:
  • Currently Being Moderated
    May 3, 2012 1:21 PM   in reply to Armin-H

    I'm agreeing with Armin-H.  LR4 is running incredibly SLOW, not like LR3 for speed at all.  Just making brush or cloning adjustments causes a 3-5 second lag for them to take effect.  Not acceptable for Adobe products.  I'm running  Mac Pro QuadCore Xeon w/ 11GB or RAM.  That should be sufficient to tame just about any beast of a program.  The lag occurs even without any other programs running.  Why should that be? 

     
    |
    Mark as:
  • Currently Being Moderated
    May 3, 2012 1:31 PM   in reply to rbphotog

    They need to clean up the code....it's just sloppy coding. There should be no reason that LR4 causes this kind of havoc on such large machines.

     
    |
    Mark as:
  • Currently Being Moderated
    May 3, 2012 1:42 PM   in reply to BCormier

    LR4 is unacceptable, RC1 or 2 — doesnt matter.
 Clealry this product was rushed to support the new cameras (and thus forcing owners of those cameras to upgrade) because it is not ready for actual use whatsoever.

     

    It's really questionable releasing software that is clearly not working as it should when a simple camera update of RAW support for the new Nikons and Canon for LR3 users would have sufficed. Clearly, Adobe saw the opertunity to get a large number of people to pay for the new version... in spite of it's failures.

     

    I am a working professional so my interest in this is beyond passive, and while I can tell you I would happily upgrade (and have - though, not happily) to gain new features and enhancements, I dont enjoy being forced to do so when that comes at the price of a massive performance failure in professional workflow. Software that works great and is priced fairly (one thing I will commend LR4 for being...) sure thing! sign me up, take my money. no worries. — but only when it works correctly and speedily.

     

    I'm quite disappointed, and negatively affected work wise.

     
    |
    Mark as:
  • Currently Being Moderated
    May 3, 2012 1:48 PM   in reply to jameskachan

    Just so you all know, the Lightroom team are aware of these issues and are working to try and allevaite them.

     
    |
    Mark as:
  • Currently Being Moderated
    May 3, 2012 2:18 PM   in reply to BCormier

    I shoot a lot and process a lot. Wish it was more, but I'm staying busy. At first LR4 was unacceptable. Now with LR4.1 RC, the performance issues are long forgotten. The only thing that reminds me of my previous issues are the pesky notificartions every time someone posts in this thread. If my 4.1Rc is slower than 3.x, I just don't notice anymore. The AMAZING color temp brush alone is worth a 20% hit to speed and performance for me.

     

    Why don't ya'll quit ******** and start working.  Perhaps you too will find the enhancements worth the percieved diminished performance.

     
    |
    Mark as:
  • Currently Being Moderated
    May 3, 2012 2:58 PM   in reply to Geoff the kiwi

    "Just so you all know, the Lightroom team are aware of these issues and are working to try and allevaite them"

     

    Yes, certainly.. Adobe couldn't let LR4 in such a bad situation ? LR4 RC2 is the worse thing I've seen from Adobe, curious distorsions on some images with Lens correction (from Adobe) and a very very slow process, with even a little database (less than 1000 images), particularly when you switch from one modul to another. It is soooooo looooong. I don't have these issues with LR3 nor ACR in CS5, with same images of course. So LR4 is now deinstalled and I will nomore use it until all things are corrected and this post concerning "LR4 slow" will be closed definitively.

     

    I don't really understand why Adobe sale this kind of not finished software ? Why haven't they wait until this beta version is ok to bring it to the market ? I feel this LR4 RC2 is a BETA version and IT IS.

     
    |
    Mark as:
  • Currently Being Moderated
    May 3, 2012 3:14 PM   in reply to Wanchese West

    Quote:
    Why don't ya'll quit ******** and start working.  Perhaps you too will find the enhancements worth the percieved diminished performance.

     

     

     

    Huh?

    Why don't we what?

     

    NOTHING is worth a 20 second freeze just because I chose another photo in the filmstrip....for me LR3 was light greased lighting...LR4 is (and I don't throw this word around easily) UNUSUABLE....period.

     

    I can't afford to move a slider and have the screen go black and redraw, the CPU peg at 100% for 20 seconds only to find out that whatever amount of slider I changed wasn't correct.

     

    I love the enhancements, but THOSE ISSUES clearly aren't even close to being worth it for me.

     
    |
    Mark as:
  • Currently Being Moderated
    May 3, 2012 3:55 PM   in reply to rpavich1234

    "Why don't ya'll quit 'female dogging' and start working." Apparently the robo-moderator removes most colorful language.

     

    I guess if I had the problems yuo described, I'd be logging some complaints too. My system is your standard 8 core 12gig Windows pos. My catalog is 413,000 images strong, so I did not elect to convert to the new process. Maybe that is what is saving me.

     
    |
    Mark as:
  • Currently Being Moderated
    May 3, 2012 4:14 PM   in reply to Wanchese West

    Yes...I've heard that going to the old 2010 process is much better and on my machine it is much improved...but not nearly like LR3...it's only "better" but not useable.

     
    |
    Mark as:
  • Currently Being Moderated
    May 3, 2012 4:32 PM   in reply to rpavich1234

    Then I just have to thank my lucky stars, 'cause I'm going to be tuning and tweaking photos for the next 36 hours and LR 4.1 RC is working for me. A cyclist in Adobe kit rode past me during an event on april 14th. I yelled out "Hey Adobe, fix LR4!" He turned and siad that he was on the LR team and that they are working on it.

     

    Maybe he shoulda' been off the bike and back in the office!

     
    |
    Mark as:
  • Currently Being Moderated
    May 3, 2012 8:48 PM   in reply to BCormier

    LR 4.1 RC2 is a pig compared to 3.6.  I'm seriously thinking about going back to 3.6 until Adobe remembers how to write software again.

     

    Now I'm wondering if I could get CS 6 given the seeming decline in quality of the Lightroom line.

     
    |
    Mark as:
  • Currently Being Moderated
    May 4, 2012 8:48 AM   in reply to CodeThought

    Ditto, I don't really need the catalogue, I thought Lightroom would have sorted this out by now, do you think I would get a refund from Adobe for Lightroom 4 and put it towards CS6 and I would get all the extra features as well.

     
    |
    Mark as:
  • Currently Being Moderated
    May 4, 2012 9:06 AM   in reply to Robbie2006

    I'm not going to bother with a refund.  I'm sure in time a well working version will materialize . The fact remains that this was in no way ready for release. But with that said I do like what I see from what I have used it just needs to be fixed. Untill then I have my 3.6 ..

     
    |
    Mark as:
  • Currently Being Moderated
    May 4, 2012 9:06 AM   in reply to Geoff the kiwi

    Does the awareness of which you speak include the horrendous coding error of 

    not stacking/queuing the mouse pointer position along with the mouse action 

    request?  It is unconscionable that such a mistake was in any versions, let 

    alone all versions to date.  Being such a fundamental and basic programming 

    tenet, we'd fire the code PM w/o a 2nd thought.  Programmers certainly are 

    not what they used to be.

     

    Being so blatantly obvious, I wonder if that wasn't intentional so as to 

    cover up the very bad program design of the right panel update which 

    accounts for m of the reported slowdowns.  To wit:  When you quickly change 

    selected images, you cah see first hand, the manic gyrations of the panel 

    caret as the system tries, bit fails, to move to selected keywords.  But 

    that doesn't work anyway so why try until yoi recode that logic.    

     

    Sent from my Verizon Wireless 4G LTE DROID

     
    |
    Mark as:
  • Currently Being Moderated
    May 11, 2012 4:26 AM   in reply to CR Henderson

    But have you updated it to the 2012 processing yet? I think earlier on in this thread someone mentioned that was when they experienced the lag/issues.  I noticed that same thing with mine.  When it offered to update my photo processing to the 2012 I decided to give it a try for the first time.  This is the only time I experienced the lag. I think this is what the issue is.  Prior to doing this, my other photos had no problems being edited in the 2010 processing version. I hope it gets fixed soon.

     
    |
    Mark as:
  • Currently Being Moderated
    May 11, 2012 4:56 AM   in reply to Natsukashi53

    I've done it both ways...2010 and 2012 and 2010 is better but it's not good...lags, choke ups....not responding....waiting.....waiting...screen redraws that are painfully long.

     

    I'm back on LR3.6 and it's LIGHTNING FAST....GREASED LIGHTNING....no comparison...not even in the same universe.

     
    |
    Mark as:
  • Currently Being Moderated
    May 11, 2012 5:21 AM   in reply to rpavich1234

    I agree. but I don't want to go back and forth between the "same" software. I understand your frustration. I guess I didn't notice it as much because I just recently tried to edit a set in the 2012 version for the first time. definitely frustrating.

     

    Sent from my iPhone

     
    |
    Mark as:
  • Currently Being Moderated
    May 11, 2012 5:38 AM   in reply to Natsukashi53

    Lol...Nobody wants to go back and forth...myself included but there is no way to get editing done in any timely fashion when each mouse click is several seconds to 20 seconds long! I'd MUCH rather pretend that LR4 didn't come out while they work out the coding bugs.

     
    |
    Mark as:
  • Currently Being Moderated
    May 11, 2012 7:06 AM   in reply to rpavich1234

    I wish I knew what the problem was -- it is very strange -- myself and many others have no problem at all.  I have both 4 and 3.6 available to me and I can see no difference in time in develop, with the sliders, with refreshing etc.

     

    So this is not something inherent in the basic design, it "basically" works just fine.  Something is occurring for some people -- the interesting is what is the "something"??

     
    |
    Mark as:
  • Currently Being Moderated
    May 11, 2012 7:17 AM   in reply to Dennis Smith

    Same for me, I see no real difference between 3.6 and 4.1RC, in fact if you

    forced me, I'd say 4.1RC is faster on my machine.  It has to be a bug that

    only affects certain configurations, and ironically, the higher the specs

    on the machine, the worse it seems.  I makes me very curious.

     

    Almost seems like a task scheduling issue or race condition when there are

    multiple cpus or more than 4 cores involved.

     

    My setup is very modest, mid 2011 27" iMac, 3.1GHz i5 and 12GB RAM.

     
    |
    Mark as:
  • Currently Being Moderated
    May 11, 2012 7:25 AM   in reply to gregkmeyer

    my setup is considerably slower than yours.

    I have a

    2011 MacBook Air 11.6"

    Core i5 1.6ghz

    256GB SSD

    4GB RAM

    Intel HD Graphics 3000 364mb alotted

     

    and it does this to my system.  I updated my catalog and optimized it.  For

    me, I only started to notice the lag once i clicked on the option to update

    photo processing to the 2012 process.  Then everything got considerably

    slower. I want to open the catalog back up in my 3.6, but I'd have to redo

    all my edits.  It's really frustrating.  I shouldn't have selected the 2012

    process option.  I think that's the key point for me.

     

    I use it on my

    Mac Mini 2011

    2.5Ghz Core i5

    500GB HD

    4GB RAM

    ATI HD graphics card.  I think it was the 4650, not 100%.  But it is

    definitely better than my macbook air's graphics card and it's discrete

    (dedicated).

     

    I still get the same kind of lag on that as well... Don't know what the

    difference is... I think it's the fact that I selected process using 2012

    process.  not 100% sure though.  I'll leave the deductions to the Adobe

    Techs to figure out.  I'll provide whatever info I can.  I just want the

    problem fixed so I can continue on with my editing.  I didn't buy LR4 to

    only have to go back to LR3. know what I mean?

     
    |
    Mark as:
  • Currently Being Moderated
    May 11, 2012 7:27 AM   in reply to gregkmeyer

    Does it matter that I'm running OS X 10.7.3? What version of OS X are you

    all running? Did you stay on Leopard/Snow Leopard?

     
    |
    Mark as:
  • Currently Being Moderated
    May 11, 2012 8:01 AM   in reply to gregkmeyer

    The fact that it "seems" to be worse on higher end machines may actually be reasonable.

    Scheduling algorithms and often multi-process applications are written to fit certain response times.

     

    Our office has run into such a case.  We run a high performance object database.  It runs really well

    on SSD's -- "except" that if you run some task that runs for a long time and does lots of disk accesses

    it kills most other sessions -- because, we think, it hardly ever gives up the CPU to wait for disk accesses.

     
    |
    Mark as:
  • Currently Being Moderated
    May 11, 2012 8:08 AM   in reply to Dennis Smith

    Other "sessions" as in other applications? or are you referring to

    read/write sessions?

     

    either way, my macmini does not have a SSD and it is also experiencing the

    same issue.

     

    CPU access is not tremendous however, and it does not show in the activity

    monitor as I edit. No spikes that I can find so far.  I will still check to

    see if I get the spikes.  But currently I am not running any other

    applications except LR4 on my MBA.  It's strange to me that LR3 worked

    perfectly fine, and LR4 doesn't.  I hope an Adobe Tech is reading this

    forum/thread.

     
    |
    Mark as:
  • Currently Being Moderated
    May 11, 2012 8:23 AM   in reply to Natsukashi53

    all- I mean no offense to any of you but I'm in the camp that has the problem and trying to hypothesis the root cause of the issue for over 2 months now is something you are certainly free to do but 1) Adobe doesn't look here; 2) Other users have yet to be able to solve it or understand root cause and 3) Lets be optimistic that Adobe is smart enough to understand all of the possible causes since they are a applcation developer and are working on it.  My net point is, I think the best course of action is to post your concern or status on the Lightroom bug/problem website which is the one that is actually monitored- not here.   I subscribe to this thread just in case there is in fact a post entitled "problem solved!!"...but after over 2 months of waiting I'm not hopefull at all.  I've already goten a refund on 4 and am back on 3.6 and am very very unhappy esp when trying to process RAW files from my new Canon 5D MIII !!!

     

    If you really are compelled to share your HW config and hypothesis, pls do so on the forum that counts in this case so that Adobe doesn't forget us..I am certainly envious of those that don't have this problem and I congratulate you but there are MANY of us that do and I really would appreicate if you post your ongoing issues here:  thx!

     

      http://feedback.photoshop.com/photoshop_family/topics/lr4_0_reacts_ext remely_slow

     
    |
    Mark as:
  • Currently Being Moderated
    May 11, 2012 8:47 AM   in reply to andreas603

    no offense andreas.  i get the feeling you're tired of getting the email

    notifications from our convo on this thread.  we're still going to rant, i

    mean, the more that people can contribute, the more likely someone could

    find a solution.  giving out configs helps other users differentiate their

    setups, which in turn helps find a particular commonality between them,

    thus finding something that may lead to a solution.  maybe turn your

    notifications off for a little while, then come and check back later, so

    that your mailbox isn't getting spammed with our conversations and rants.

     

    I think that part of the reason people are ranting here is because we all

    share a common issue, and it feels good to vent to someone who understands

    your pain... if you were to vent to your gf/bf who doesn't know anything

    about what you're talking about and can't relate, you wouldn't feel

    satisfied and would be more frustrated.

     

    In the lightroom feedback forum, this issue has been posted if i remember

    correctly.  I saw it there when I was looking for this thread.  I don't

    think that posting new threads for the same thing will speed up the Adobe

    Tech's fix process...but I agree that posting our configurations there as

    well may help them narrow down the issue.

     

    That being said, I don't think it is pointless for us who have the problem

    to continue to rant/vent here... It's a thread to talk about the problem,

    share our experiences, and provide any additional insight that could help

    resolve the issue...

     
    |
    Mark as:
  • Currently Being Moderated
    May 11, 2012 9:02 AM   in reply to Natsukashi53

    Natsukashi53 - as you can see I'm stil subscribed

     

    Points taken... just as a quick point of clarification, I was not suggesting to start any new thread anywhere..thats the last thing we need...but instead to continue to 'rant' (or copy your rant from here) and double post it to a place Adobe monitors- granted if I worked there, I'd prob tune everything out at this point!

     

    One thing that I did suggest to Adobe 3-4 times now but they haven't taken the bait yet (and I'm not smart enough to do it or I would) is to provide those willing to give feedback ( alot of us!) a format or template such that we each provide the *same* type of information about or environment/config... I can't possibly imagine Adobe being able to easily analyze root cause with everyong providing random HW config status, logs, etc... How can they (or us as a user group) try to get to the bottom of this when information is streaming in in bits and pieces from everyone.  Wouldn't it be nice to be able to more or less fill in a template (or heaven forbid allow us to provide our HW config ONCE in our profile so we dont have to repeadly do it) and for all of us to have a better basis for developing our hypothesis?  There are a lot of smart people here!

     
    |
    Mark as:
  • Currently Being Moderated
    May 11, 2012 9:12 AM   in reply to andreas603

    true. I see your point.

     

    Sent from my iPhone

     
    |
    Mark as:
  • Currently Being Moderated
    May 15, 2012 10:58 AM   in reply to Natsukashi53

    Well I'll chime in and say that I've noticed 2 things. My SSD gets eaten up (went from 130gigs free to a handfull before I tracked it down) by a temp file that is created since I installed RC2 and I have actually run out of ram... that is fricken nuts because I have alot of ram!

     

    Winders7pro

    intel core i7 970 (3.2GHz times 6 cores)

    24GB ram (I've been at 99% used a few times since RC2 install).

    GeForce GTX 570

     

    I've got all the settings in both CS6 and LR4RC2 maxed out to allow full usage of everthing (it is an editing machine after all!).

     

    I sure hope they fix these leaks soon, I love most of the new updates in both products.

     
    |
    Mark as:
  • Currently Being Moderated
    May 17, 2012 4:59 AM   in reply to rpavich1234

    rpavich1234 wrote:

     

    I'm back on LR3.6 and it's LIGHTNING FAST....GREASED LIGHTNING....no comparison...not even in the same universe.

     

    This is mostly offtopic reply, but I'll take the risk I'll anger you all.

     

    Yesterday I booted up my old windows machine (WXP, core 2 duo around 2,4 GHz, 4Gb ram) and tested old Lightroom 2.3. Man it was fast when comparing even 3.6.

     

    I have always thought that every new major version is a bit slower than previous. In every software, not just LR.

     
    |
    Mark as:
  • Currently Being Moderated
    May 17, 2012 7:12 AM   in reply to KKuja

    It was the same on iMac. 2.6 was fast as nothing which was slowed down with the introduction of rel. 3. It gets worst with every release. Release 4 is just a nightmare. I upgraded my memory from 8Gb to 16Gb but LR4 doesn't get impressed by doubling the ram.

     
    |
    Mark as:
  • Currently Being Moderated
    May 17, 2012 6:47 PM   in reply to BCormier

    Somehow I stopped getting email updates on this thread for a few weeks, not that it seems to have mattered as nothing has changed. I'm not a professional photographer, but I have a serious backlog of work that I'd like to get done, and try as I might LR4 is just not making it easy. I've already complained about the slow slider response in the Develop module, and the speed by which Quick Develop changes happen in the Library module. But OH...MY...GOD...if I make a white balance change in quick develop...I...might...as...well...get...a...coffee. Right now I'm applying a tweak to a few hundred photos, and LR4 has basically shut down on me. It's doing its thing, but I can't browse photos, apply ratings, add keywords, or anything else constructive while it's applying the WB changes. WTF Adobe? Is anyone still working on this? It's been nearly a month since 4.1rc2 was released.

     
    |
    Mark as:
  • Currently Being Moderated
    May 18, 2012 12:31 PM   in reply to JustinDustin

    Don't know if this will help anyone but Lightroom 4 was very slow on my machine which is not the highest spec in the world but I was in preferences / file handling and discovered that my cache memory  on my drive was

    ( drive N / Adobe raw cache ) so I had a look for the cache folder and couldn't find it so I created a cache folder, incresed its size to 20 gig and tried Lightroom 4 again and my PC is running much faster,I can go between grid and develop as quick as I could in Lightroom 3.6, I can now zoom instantly without a two second lag, certain sliders in the develop module are still a little bit jumpy ( I'll leave that one to Adobe ) but overall a huge improvement.

    Hope this helps.

     
    |
    Mark as:
1 ... 13 14 15 16 17 ... 43 Previous Next
Actions

More Like This

  • Retrieving data ...

Bookmarked By (3)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points