Lightroom 4.1 very slow performance in develop mode

  • 17
  • Problem
  • Updated 6 years ago
  • (Edited)
I upgraded from LR3 (latest version) to LR4.1 because I needed support for my Canon 5DMIII. I upload files and have them render 1:1 previews. In Develop mode moving from one file to the next is excruciatingly slow. it used to be instant in LR3. I alternate between 10-22 megapixels RAW files. I have done everything in the Adobe optimization PDF. This is delaying my workflow way too much! what is the solution? I have a PC running a core i7 processor on windows 7, 64 bit. 16G RAM, new good video card.
Photo of Andrea Taylor

Andrea Taylor

  • 10 Posts
  • 0 Reply Likes
  • extremely upset!

Posted 6 years ago

  • 17
Photo of slarti3

slarti3

  • 13 Posts
  • 4 Reply Likes
Try make sure that the actual size (in pixels) of your develop preview is LESS than a quarter of the image resolution, both horizontal and vertical.
Your images are 5760 x 3840 pixels, so make sure your develop preview is no more than 1440x960.

This can speed up things 4x if you're at 1441x960 pixels for instance.

I had to to this when I moved from a 1920x1080 to a 1920x1200 pixel screen.
Photo of heyix

heyix

  • 10 Posts
  • 0 Reply Likes
I've got the same issue - the develop mode is awfully slow (contacted the support via phone and made many settings from the replied help-side: http://helpx.adobe.com/lightroom/kb/o....

Rendering the previews in 1:1 speeds up the library, but not the develop-engine. Sliders/buttons react at best 5-7 seconds after loading the image or later...
(WIN 7 pro 2x Quadcore Xeon, Images and catalog(s) on 1TB WD Caviar Black 7.200 rpm 64MB)

The german support has no further idea!!!

So guys, what can I do to speed up LR4.1 (the same images in a fresh new catalog load in LR 3.6 30% faster, in LR 2.7 50-60% (2-3 sec.) faster).
Photo of Andrea Taylor

Andrea Taylor

  • 10 Posts
  • 0 Reply Likes
I also experience a lot of "jerk" in the mouse... not sure if related or not. Just a new thing since 4.1
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 379 Reply Likes
Andrea, the problem is not "user error" - it's bugs in Lightroom. *but* not everyone is being bit by them, which means these bugs only bite because of things encountered in *your* system (and other people's systems who are having problems...). That doesn't mean it's your fault, or you should have to solve them not Adobe..., but it *does* mean you may have the power to get around them, if you have the technical ability, and time/money/inclination...

Definitions:
* 'it' - usually many things, a combination of which, or any one of which may cause like symptoms.

I'm sorry I am not more help. Good-bye for now, and good luck...

PS - Try removing your mouse.

Rob
Photo of Andrea Taylor

Andrea Taylor

  • 10 Posts
  • 0 Reply Likes
Thanks Rob. It definitely seems to be affecting people suing full RAW files from the new 5DMIII - At least that is where I am hearing the most complains from... though I know of some Nikon users that went back to using LR3! Unfortunately I do not have that luxury because of the new files.

One thing that was mentioned to me is to completely uninstall LR and make sure all files related to it are deleted from my system and then reinstall. I was using the Release Candidate version before the final 4.1 candidate came out, and someone at Adobe said that may be causing the issue... it is my next step. And could be a reason why this is not affecting everyone. Would be interesting to know if those with/without the problem have used the beta or release candidate for 4.1 before the formal update.

I do not have the knowledge to deal with this, but my husband does (computer wise, though not Adobe products specific) so he has been trying to help me out... time and money are a different issue altogether :)

Thanks for chipping in!
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 379 Reply Likes
It could very well be that there is one or more bugs in the 5DMIII handling code.

Have you tried it with raw files from other cameras?

I agree a fresh install, after a thorough "cleanse" is a great idea - bugs in previous versions can cause problems that bugs in current version are tripping over. I've been using Lr4 since the beta, but then I've also rebuilt previews, cache, exported catalog, ... I didn't have to delete prefs, since some bug in Lr deleted them for me ;-}

Cheers,
Rob
Photo of Andrea Taylor

Andrea Taylor

  • 10 Posts
  • 0 Reply Likes
I have Prefs backed up so I hope to b able to use those if I rebuild. It definitely is my next step. It is just a question of juggling time and jobs... though if this works it'll save me lots of time! Thx again!
Photo of Jeffrey Rueppel

Jeffrey Rueppel

  • 3 Posts
  • 0 Reply Likes
Andrea's response above is spot on for increasing the speed in Develop Mode.

You can access this feature quickly at:

Lightroom -> Preferences -> File Handling -> Camera Raw Cache Settings.
Change the default Maximum Cache Size from 1.0GB to 10.0GB
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 379 Reply Likes
This works for some folks, others: not so much... - you got lucky...
Photo of Andrea Taylor

Andrea Taylor

  • 10 Posts
  • 0 Reply Likes
I guess I did. It works much better than before... though it is still not up to par with what LR3 was! So it definitely still needs improvement.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 379 Reply Likes
Hi Andrea,

Some things will probably never be on par with Lr3, because they require more CPU, so "running normally" may be the best you can expect.

But if Lr4 is more than say 30% slower than Lr3, it's probably not normal yet.

Rob
Photo of Andrea Taylor

Andrea Taylor

  • 10 Posts
  • 0 Reply Likes
Definitely slower. And I actually just went from running LR3 in a Core Duo machine to now having an i7, and from 8G RAM to 16! Plus newer and faster hard drives! All internal.
Photo of heyix

heyix

  • 10 Posts
  • 0 Reply Likes
I haven't said that I sat the cache up to 50 GB and put it onto the WD Black Caviar (at 1 TB 50gig's don't matter) - no improvement on speed in the develop module....

Perhaps my issue is related to the dual monitors: I've 2 24" Dell Ultrasharps conected via DFI. I read sth. about problems with that configuration.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 379 Reply Likes
1. I once got some performance improvement by moving the cache to a different drive. I then moved it back to where it was and improvement was preserved. Sometime it's just a matter of shaking things up - you force it to do something different and something else gets ironed out...

2. Try uninstalling one monitor. (I run with 1 2407(vga i/f) & 1 2408 (dfi) - no problems, *but* it may be the driver not the monitors at issue.
Photo of heyix

heyix

  • 10 Posts
  • 0 Reply Likes
Thanks Rob, I tried it, but got no improvement. By the way I saw sth. strange: My cache-folders (either on C: or H: (WD Black Caviar)) contain no data!!! They were completely empty (no hidden files, not any files). Why doesn't LR use this cache.

Any further checkbox or setting what I do have to activate?

I read about that LR uses the cache to rebuild the images faster - why does my version leave this option out?

This afternoon I deleted all my nvidia driver updates down to the blank videocard driver of WIN 7 - no improvement. Reinstalled the latest 296.88-quadro-tesla-win... got not better... :-((

It's no difference if I run one monitor or two.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 379 Reply Likes
What caused me to move my cache, way back when, was that it was not being used. Same symptoms: no files ever written to it. So, consider moving your cache and see whether Lr will be willing to start writing / reading from it at the new location. In my case, I got lucky, and I was able to move it back to the old location and it continued to write / read it there - YMMV.

There is no enable / disable option-pref, just cache location and size.

Sorry about lack of improvement otherwise...

PS - Sometimes its an older driver that works better than the latest ;-}, sorry things aren't better...
Photo of heyix

heyix

  • 10 Posts
  • 0 Reply Likes
Hi Rob,

thanks again for your help. Yesterday I made serveral adjustments to my system (cleaning up some space and the registry, deleting unused tools and software, etc...) and installed 3 small gadgets to have a live-view how my workstation (Dell Precision 490 with 2 Xeon Quadcore, Nvidia Quadro FX 3450) is stressed by LR - let me do a quick report:

1) LR doesn't use it's cache folder (set to 50GB) either on C: or H: (I can clean the folder by the 'clean-button' in LR, but LR writes no data in/back)

2) My physical RAM is only used to 73-78%

3) The CPU's: For a fragment of a second up to 100% - mostly at 5-20%

4) GPU: 243MB of 256 MB free - FanSpeed at 30% --> low usage

5) HDD: For a fragment of a second up to 90% - mostly at 5-10%

So there is definately no stress to my system! Lightroom leaves out many available ressources! I contacted the german support and reported this behaviour. They asked for my msinfo-file to have a look at the performance. I send it to them - hope they find a reason. I'll keep you (all) in touch...

BR
heyix

P.S: Removing/installing LR doesn't fix the (dis)usage of the cache :-((
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 379 Reply Likes
Hi heyix,

I wish I knew what to say - sounds like things are not quite right, but I dunno why, and you already knew that. Perhaps the deafening (Adobe) silence around this issue of late means Adobe will be out with 4.2 soon that will help.

Sorry I'm not more help.
Hang in there,
Rob
Photo of Robert Frost

Robert Frost

  • 392 Posts
  • 51 Reply Likes
A couple of comments for Heyix.

The ACR cache folder is only used to store part-rendered raw files (produced while rendering previews) that might speed up 1:1 rendering in Develop. It is not used for DNGs or JPGs, or for caching anything else. When you render previews, as well as storing the previews in the previews folder, if the images are raw files, then the intermediate xxx.dat files are made and stored in the acr cache folder, and used to speed up future rendering instead of having to start with the raw file again.

Have you tried turning off the filmstrip and navigator panel? These have to updated along with the screens on your two monitors and the histogram. Some people have found turning them off reduces the load on the graphics and speeds things up considerably.

I've noticed several people with twin Xeons, Macs and PCs, complaining of poor performance. Perhaps there is a problem with twin cpu machines. How does it perform for you on an ordinary single cpu machine?

Bob Frost
Photo of heyix

heyix

  • 10 Posts
  • 0 Reply Likes
Hi Bob,

thanks for the explanation how LR uses the cache folder.

I tried the filmstrip/navigator option and tested the speed in develop mode:
Speed increase maybe at 1 second less to load (always the next) image - but 6-7 sec. still quite long. Switching to 2 monitors slows completely down. LR chrashes --> after restart many images got a little exclamation mark in the upright corner (error by reading the image) --> again shutdown and restart --> marks are gone, but LR as slow as before. That doesn't solve my problem.

I only use multicore PC's. I have to ask some friend to test LR on his single CPU PC. Will do it at the weekend...

heyix
Photo of Andrea Taylor

Andrea Taylor

  • 10 Posts
  • 0 Reply Likes
Check out this transcript from a conversation with Adobe Spport someone posted in another forum.
I tried this yesterday and it seems to have sped things up but I am going to be editing a large job this afternoon and I'll test it really well then.

However you may want to give this a try.

William: I understand that you're experiencing performance issue. Am I correct?
Jojo: Oh yes
William: Please close all windows except this chat window.
William: Click on Start button.
William: Type %appdata% in the search box and press Enter.
William: Double click on Adobe folder.
William: Check for the folder of Lightroom and rename it to "OldLightroom".
William: Click on Start button.
William: Type %temp% and press Enter.
William: It will open Temp folder.
William: Empty the files and folders inside it.
Jojo: ok done. it still has files that could not be deleted for Win Explorer and Google Chrome (the browser I use)
William: Okay.
William: Launch Lightroom and check if you're getting the same issue.
Jojo: that seems to have sped it up significant;y
William: Perfect.
William: Please double check if that works fine now.
Jojo: Much faster, but all of my presets are gone
Jojo: Export presets, etc
William: It was due to corrupt preference that was causing this issue.
William: Close Lightroom.
William: Click on Start button.
William: Type %appdata% in the search box and press Enter.
William: Double click on Adobe folder.
William: Check for the folder of Lightroom and rename it to "2OldLightroom".
William: Now check for the folder "OldLightroom" and rename it to ""Lightroom".
William: After that open Preferences folder inside it.
William: Check for the file "Lightroom 4 Preferences.agprefs" and rename it to "OldLightroom 4 Preferences.agprefs".
Photo of Frederic de Laminne

Frederic de Laminne

  • 1 Post
  • 0 Reply Likes
Andrea, can you provide some feedback on this ? Did it work for you ?
It didn't change for me.
Photo of Andrea Taylor

Andrea Taylor

  • 10 Posts
  • 0 Reply Likes
It seemed to make it faster. We tested it, the opened LR 3.6 and the speed overall in develop mode going from image from image seems similar. Maybe 1 second slower for 4.1, however, I still feel that overall the performance is slower. When I move sliders it takes time to react and it takes also quite a while and sometimes several tried to paste setting from the previous image into the next one. So overall, my workflow is still slower. I know this is not a great answer. I am not sure what is going on. But I am working slower now than I used to when I had 3.6
Photo of heyix

heyix

  • 10 Posts
  • 0 Reply Likes
Hi Andrea,

I tried this (takes only 3 minutes), but it doesn't affect my speed. The images always load 7-8 sec. each in the develop module.

Thanks
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 379 Reply Likes
I know one person who sped up Lightroom performance by running 4.1 in a virtual machine (e.g. vmware).

Note: If Lightroom is performing normally, this will make it worse, but if it's already really bad, this may make it a lot better.
Photo of Matthew Kieffer

Matthew Kieffer

  • 5 Posts
  • 0 Reply Likes
I am running an 8 core with 16 gigs of RAM and 2 way SLI. I have an SSD for caching, and the pictures I edit are on separate drives from the primary. I am editing 14 bit NEF files. Export times are really slow compared to LR3. The sliders start out fast, but after a few minutes they start to get sluggish. I do have dual monitors and a Wacom Intous 4(which caused issues in LR 2 and 3). If it were just the slow responsiveness, I would not be all investigative... it is that paired with the export that leads me to think something needs fixed in the engine! Camera RAW does not have issues in Adobe Bridge or when opening up and adjusting in PS. So, I have trouble with the fact LR has bad performance when the others do not. I am being patient though.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 379 Reply Likes
|> "The sliders start out fast, but after a few minutes they start to get sluggish."

Definitely something not right.

How's memory consumption? leaking?

Maybe try disabling Wacom - they've been a problem point for some.

PS - If exports are a lot slower, then performance is abnormal. A little slower is normal, due to extra processing.
Photo of Bruno Pimentel

Bruno Pimentel

  • 1 Post
  • 0 Reply Likes
And i was thinking my Hardware was the cause of slow performance.. Well u guys have to fix this.. :(
Photo of F R

F R

  • 3 Posts
  • 0 Reply Likes
I have been successfully using Lightroom 3.6 for a year and installed Lightroom 4.1 trial.

I made two folders and copied the same set of 100 Canon 5D MkII RAW images into them and tried editing them in 3.6 and 4.1

I've noticed a dramatic slowdown in performance in 4.1 compared to 3.6.

Everything from zooming onto an image, adjusting develop sliders to cloning and spot healing is almost instant in 3.6 but takes dozens of seconds (with spinning beachballs) in 4.1.

This is currently preventing me from upgrading to 4.1.

I have a 2010 12-core Mac Pro with 16GB of RAM running Mac OS 10.6.8.

Judging from the number of posts in the Adobe Forums - this sounds like a known issue.

Any suggestions on things to try?

Is Adobe currently working to fix this issue?

.

This reply was created from a merged topic originally titled
Lightroom 4.1 considerably slower than 3.6.
Photo of SamC

SamC

  • 2 Posts
  • 0 Reply Likes
Lightroom 4 is unusable. Specifically the Develop module. It takes 15 to 20 seconds to load each image. (1:1 created on import). Every adjustment hangs. I was on with support for about an hour and a half last night getting generic answers. Your support people don't seem to be knowledgeable. Still waiting for a call back from an expert..but looking at forums..this seems to be a pretty popular problem. IMO...LR4 should not have been released yet.

This reply was created from a merged topic originally titled
Lightroom 4 Develop Module performance.
Photo of ritom

ritom

  • 2 Posts
  • 0 Reply Likes
I installed LR 4.1 as an upgrade to LR 3.5 and although it's new process helps a lot with soome pictures, it is incredibly slow e.g. when switching between pictures taking 10s or more to load a new picture on my iMac 3.6GHz which is less than one year old! LR 3.5 was pretty fast on that machine and I hope LR 4.X will catch up soon!

This reply was created from a merged topic originally titled
LR 4.1 incredibly slow.
Photo of brian brains

brian brains

  • 69 Posts
  • 5 Reply Likes
LR4.1 Win7 64 16Gb RAM

In the Develop module, adjusting any adjustment slider often causing the whole panel to grey out and jump or jitter. Often the mouse fails to 'grab' the slider and the adjustment doesn't get made.

I suspected several things so removed Windowblinds, reinstalled my AMD 5700 series driver, removed Catalyst manager and rebooted. LR behaved itself for a while then gradually the problem became worse till it was unusable. I also noticed the 'Loading' popup appeared more and more.

This reply was created from a merged topic originally titled
Lightroom: 4.1 develop module slider response (Win).
Photo of colblip

colblip

  • 9 Posts
  • 2 Reply Likes
I find the LR 4.1 manual lens correction to be virtually unusable. The sliders are very sluggish and 'jerky'. When I finally get a slider to move the resulting change on the screen takes >10 seconds to occur.

Are others having this problem. Appears to me to be a major bug.

BTW, were does one submit bugs to Adobe?

Thanks.

This reply was created from a merged topic originally titled
LR4 Manual Lens Correction Unusable.
Photo of Alik Griffin

Alik Griffin

  • 3 Posts
  • 0 Reply Likes
I get this problem on and off. It's not all the time. I went out and took a batch of around 500 photos today. Could not edit them for the life of me. Too slow. So I broke my folder down into smaller ones of about 200 photos. Re imported those and my speed returned. Let me know if this works for you.

I know it has nothing to do with system resources. I have an 8 core macpro with 24 gigs of ram with solid state as my workstation. Still slow on those.

I've compiled a list of solutions to this problem on my site: http://alikgriffin.com/solutions-ligh...
Photo of Rick Sandberg

Rick Sandberg

  • 1 Post
  • 0 Reply Likes
I process hundreds of raw hockey pictures at one time.
I'm still refining the process but I can tell you this:
- set to render 1:1 previews on import.
- do not apply ANY presets during import.
- wait until the last possible moment to use noise reduction or any other math intensive operations.

These simple precautions sped things up dramatically.for me.
Hope this helps.