Lightroom Classic CC: Develop module still slow.

  • 9
  • Problem
  • Updated 11 months ago
Hello, I would like to provide some feedback on LR Classic performance. I was hoping for an increased performance and better processing optimization (at last) and maybe not having to use smart previews, but unfortunately it's still not the case.

To be clear this is not about extreme cases of various delays of tens of seconds some users are having!
From my testing it seems that it's clearly internal (long term impression) and in my experience not very config/setup specific.

I spend most of my time in Develop and my main problems with versions 4 to 6 have been stuttering, delays, freezing while going from one image to another or zooming, cropping, applying previous edits etc.
I tested Classic on 3 different PCs  with Windows 7 and 10.

First was one weaker Pentium PC (not very relevant for this)
Second - new HP desktop with Intel i5 7500. LR on SSD, 16GB RAM, Win 10.
My main computer at home - i5 4670K overclocked to 4 x 4.4 GHz, 16GB RAM and SSD, Win 7.
Both i5s have Full HD screen and only integrated Intel GPU.
Detail panel off ! (I have it disabled while editing to speed things up)
Max thread count is 3 threads curiously with this version.
Images are 24Mpx D750 NEFs.

Fresh catalog or not, the behavior is very similar and repeatable in my opinion . When you have images without any edits it's quite OK. The (familiar) delays start when you apply let's say auto tone basic edits to all images and go from there. Mainly going back and forth and zooming, which basically simulates my real work, just faster. And I can also see that in 10 minutes or so LR starts to lose breath again.

So my main observations are:

If an image has edits it takes around 4 seconds for the auto tone button to get active (good indication of rendering time). When you try to zoom (or apply previous edits, crop) at that time there's an obvious delay and some stuttering while you try to drag the mouse over zoomed image (to see other parts). But the thing is the CPU is just around 60% at that time. The processing LR is doing still appears very serial to me (all cores are active though).

A similar thing happens when you switch to following image (fit view not zoomed in) and just keep moving the cursor over the image. You can see that this basically doubles the rendering time (till auto button is active). Again CPU is at 50-60% - why is this ?!

With smart previews rendered (and use smart previews in develop preference active) the rendering times are obviously better, but as soon as you start zooming in there's still even longer delay which I'm used to from previous versions (I was hoping it will be fixed finally). Stuttering is even worse and when you try to move zoomed image it does nothing for a while or it zooms back out sometimes. It's just annoying. Going from smart preview to full render needs to be faster, really. Again CPU is not maxed at all.

Turning on GPU acceleration helps with zooming a bit, but going from one image to another is longer. It also introduces some screen flickering while cropping and such. In the end you cannot tell which option is better than the other. There's a different disadvantage to each option. And as I already mentioned it seems LR still gets slower over time. There's just something going wrong internally imho. And the overall sluggish feel is still there unfortunately. 

To be honest I'm quite disappointed with Classic (the new LR CC is not an option for me now). I'm willing to pay for the CC subscription but for now I'm staying with v6. However the other performance improvements (in library) are nice.

If anyone from Adobe needs any additional info from me, just let me know. Thank you.

Alan
Photo of Alan Novak

Alan Novak

  • 18 Posts
  • 4 Reply Likes

Posted 1 year ago

  • 9
Photo of Joel Weisbrod

Joel Weisbrod

  • 180 Posts
  • 98 Reply Likes
Photo of Alan Novak

Alan Novak

  • 18 Posts
  • 4 Reply Likes
Hi Joel, thanks. I did. I just wanted to summarize my experience.
Photo of Joel Weisbrod

Joel Weisbrod

  • 180 Posts
  • 98 Reply Likes
I am really in trouble as the Classic version is really, really slow on my PC. I just tried moving my last wedding shoot onto my old laptop and it is a little better but still too slow to use. 

I have been playing with Capture One (also non-destructive editing)  and although it is not the same it is close and it is super fast. 

Not sure what Adobe has done differently but they have not done it well.
Photo of Tracy

Tracy

  • 1 Post
  • 0 Reply Likes
Yes Lightroom used to be so fast and easy to use.
Now it is painfully slow, might have to give Capture 1 a try as this slow speed is not acceptable when I am going through the number of photos I do on a daily basis.
Photo of Alan Novak

Alan Novak

  • 18 Posts
  • 4 Reply Likes
Hi, I see similar posts regarding performance like:
https://feedback.photoshop.com/photoshop_family/topics/the-latest-lightroom-update-october-2017-has-...
https://feedback.photoshop.com/photoshop_family/topics/lightroom-class-cc-sluggish-develop-module-af...

But again as I mentioned, I don't experience such a long lags and delays. Although related to LR general slowness they seem to be more machine specific. Which brings us back to LR being apparently very sensitive to various OS configurations anyway.

I would like to ask something. Anyone feel free to post.

1) I'm wondering if anyone from Adobe staff / Lightroom team is aware of the long and annoying zooming delay with smart previews? Or other points in my original post for that matter. I would just like to bring this forward.

Or
2) How essential is a fast dedicated GPU for LR Classic now? Is there any significant improvement with a powerful GPU compared to acceleration disabled? I only tested Classic with integrated Intel graphics. Obviously I don't want to spend money on expensive unit just to find out later it doesn't really help :)

3) To other users -  How do you find LR Classic performance? But specifically in develop when images have edits and you do your real work. For example you select series of images, apply some edits (either auto tone or basic, HSL, etc.) in advance and then go forward and start real editing, zooming etc. Do you see any significant improvements over v6?

Thank you.
Photo of Joel Weisbrod

Joel Weisbrod

  • 177 Posts
  • 98 Reply Likes
Do you use Lens Corrections?
Photo of Alan Novak

Alan Novak

  • 18 Posts
  • 4 Reply Likes
Joel: When I use them, I apply them mostly after other edits on a photo and not in bulk in advance.
Photo of Robert Frost

Robert Frost

  • 396 Posts
  • 53 Reply Likes
Photo of Tom de Jongh

Tom de Jongh

  • 18 Posts
  • 20 Reply Likes
Has anyone overcome the slowness that is dogging the Develop module when open for a long time, or after editing a 30 or more photos?  I have provided information to Adobe but it has all disappeared into a black hole.  No correspondence from Adobe, and my comments are slowly moving further down the pages of other problems without any solution in sight.

Is anyone getting answers, or are we all looking at alternatives now?
Photo of Alan Novak

Alan Novak

  • 18 Posts
  • 4 Reply Likes
Robert Frost: Thanks for the link. Good test, but also generic and to be honest, it doesn't disprove my claim of slowness during actual editing.

Tom de Jongh: regarding Adobe, no response here yet. Honestly, it reminds me of their silence before they acknowledged the performance issues.
(Edited)
Photo of Venkatesh Sharma

Venkatesh Sharma

  • 2 Posts
  • 0 Reply Likes
is Adobe working this? is there any timeline for the fix to come? Lightroom in its current state is virtually unusable. if i don't hear about any target date for this fix, i am afraid, i have to move to a different image editing software. i cannot afford delay my projects by 3x-4x. 
Photo of Andrei Neamtu

Andrei Neamtu

  • 1 Post
  • 0 Reply Likes
have the same problem - booting in safe mode (win7) solves the issue.. i belive it has to do with bitdefender and/or other plugins installed. i just tried safe mode boot and works as it should, with all the downside of not using anything else..
Photo of J Ray Sanduski

J Ray Sanduski

  • 3 Posts
  • 0 Reply Likes
I am experiencing serious develop module issues too!

I have called and gone on live chat with Adobe - they do a Bomgar takeover of my machine and fiddle around with some settings, then it works ok for a while - like 50 edits or until I do an export. Then it goes kaput again with flashing screen, hangs and blips. I can not have these issues and perform as a professional photographer!

I have been editing the same wedding gallery for 2 weeks!

This needs to be fixed!

(Tech info - Win 10/i7 quad core/24gb RAM)
Ray
Photo of Tom de Jongh

Tom de Jongh

  • 18 Posts
  • 20 Reply Likes
Exactly my experience including the takeover of my PC.  I have gone back to editing with the previous version which works OK.  Let's hope there will be some action by Adobe soon.  
Photo of Alan Novak

Alan Novak

  • 18 Posts
  • 4 Reply Likes
Hi,
I'd like to share some interesting things I have found, well interesting at least for me :)

First I learned that raw decompressing is rather serial in nature (I didn't realize that before). Which slows down rendering in LR at first to some extent I guess. Is there a room for improvement here? Well I can't tell, maybe so. I have a D750 and it has compressed raw files only. I tried some uncompressed raws from D810 and the initial rendering is indeed a bit faster.
https://feedback.photoshop.com/photoshop_family/topics/gpu_mpe_support_for_lightroom_4_multiprocessor_support

I don't know how realistic it is, but Adobe is a big company so maybe there is some possibility to convince major camera companies somehow to change their raw format a little bit? :) Generally parallel processing is the future it seems.

But another thing: Let me describe my setup in LR first.
I have my sharpening and noise reduction defaults set up specific to camera ISO. During editing I have Detail panel turned off in order to speed up rendering a bit. Now I have found out that this is most probably the reason for sluggish Develop performance and the zooming delays (see my first post). 

I hope I'm not completely off the mark on this but here is what happens:
 When you have any non default value set (it can be lower, doesn't matter) especially for Luminance or Color noise reduction in advance, delays going from one image to another start to appear. The effect is noticable. LR somehow includes NR values in it's calculations but even if the panel itself is turned off! 

But there is something even more confusing here. It seems that even if you have the default values for NR (0 for Lum. and 25 for Chroma) and just turn Detail panel off, rendering gets slow again.
In the end you get the best performance with the default NR values. Disabling Detail panel has no speed benefits and it's even slower.

The way I see it, the resolution to this would be to ignore NR and sharpening values completely while calculating the auto values/rendering when the Detail panel is off. It would be logical. Now it seems it's not the case. This is effectively another source of  Develop slowness because it adds up to the initial raw rendering.  Anyone can try it (set any non default NR and go forward, zoom, drag the zoomed image, also Auto button is now active slower, etc.) 

If anyone from Adobe reads this, it would be interesting to hear from you, maybe Simon Chen ? :).
Thank you.
(Edited)
Photo of Venkatesh Sharma

Venkatesh Sharma

  • 2 Posts
  • 0 Reply Likes
Hi,

wanted to share an update. while researching on ways to improve lightroom performance (i had already tried all those configuration changes recommended by Adobe as well as others but with little success). I stumbled upon a link which described the follow step(unable to find that link now.. Sorry). Glad to say it worked for me! 

1. after importing the photos, generate the Smart previews from the library module.
2. once the smart previews are generated, go back to the folder in the windows explorer (PC) and rename it. (remember the old name for later use)
3. LR will detect that the folder is no longer existing (will show a box like icon on each photo in the film strip). but will continue to show the photos from the smart preview it generated. the original is not loaded since it cannot find it.
4. once the editing is done, rename back the folder to its original name to see full res pictures in LR.

Thats it! I can now edit the photos with much faster transition times. the unusual slowness is now gone. The downside of it though is that the pictures won't show as much quality as you would expect of the original one.

This works for me as i can live with a somewhat average quality photos during editing against waiting for eons for an image to load..  
Photo of Jerry Syder

Jerry Syder

  • 225 Posts
  • 110 Reply Likes
Venkatesh. this sound like the "use Smart Previews instead of Originals for image editing" option that was implemented. It can be found in Preferences, under the Performance tab. Depending on the version of LR you are running of course. Adobe obviously saw this benefit and were aware that users were doing as you suggested. Now, Lightroom would use the Smart Preview(instead of the hi-res file), as long as they exist of course and as long as you have that option selected in Preferences.
Photo of Ken Sparks

Ken Sparks

  • 5 Posts
  • 0 Reply Likes
The develop module is extremely slow and very annoying. Has Adobe come up with any remedy?
Photo of plutonian

plutonian

  • 1 Post
  • 2 Reply Likes
Import/Preview generate goes lightning fast for me.
The CPU goes up to 90%+ (Ryzen 7 1700X - 8 core 3.9GHz, GPU is 1060, 16GB RAM , SSD 850 EVO).
I create 1:1 and Smart previews at import, but no conversion to DNG.
Older LR only used around  15-20% of CPU when importing/exporting.
Just check 'Generate previews in parallel' in preferences > performance tab.

Develop module is another story...just unusable for any serious work.
It kinda beats the whole purpose of using lightroom for its fast workflow.
10 brushes + 10 healing spot pretty much kills it...zoom to 1:1 takes  3-4 seconds, pan is sluggish, changing between photos takes 4-7 seconds.

I have just discovered that changing Process to version 3 (2012) restores some of the develop module performance.

Another weird thing: exporting 4 files makes LR jump from 6 GB memory usage to 9 GB!
Once the export is over it keeps 7 GB memory usage.
Photo of Artur Jarosz

Artur Jarosz

  • 17 Posts
  • 4 Reply Likes
Exactly! Develop module is extremely slow! I do a lot of weddings. From one I process 500-800 pictures, multiply it by 35 gives me 17500-26000 pictures. I have to wait every time few seconds for LR to generate previews, sliders are not responding in real time for me either, crop tool starts to respond 2-3 second after being clicked, so I am wasting 15-20 second on every picture for sure. Counting that I spent about 7-8 hours daily by a computer it gives around 3 weeks!!  Only weddings season! And I don't count pictures not being processed, which I need to see to reject, etc.
To be honest, I don't understand separating Lightroom to CC and Classic. It should be one, with one checkbox - sync selected pictures to the cloud, so developers could focus on making it faster and better. I just don't get it.
I'm testing now CaptureOne. It has different algorithms, I'm used to ones in Lightroom, but it is lightning fast when I compare them.  My Adobe subscription end by April. If nothing changes, I will not renew it.
Sorry for my English, but I'm not using it very often.
(Edited)
Photo of Rolly Barayang

Rolly Barayang

  • 1 Post
  • 1 Reply Like
The only remedy for now is to restart. Edit/ Preferences/ Restart Lightroom. Seriously, I just acquired Classic CC as i thought this will fix the problem. Sadly the problem still exist.  Such a waste of money.
(Edited)