Participating Frequently

Question

Lightroom Classic CC seems slower than previous Lightroom version it replaced

Forum|Forum|8 years ago
October 18, 2017
97 replies
68776 views

Lightroom Classic CC seems slower than previous Lightroom version it replaced. To test the performance of the new classic update, I imported some raw pictures taken with a Nikon D810/D850 and am noticing that moving from one image to another (all with 1:1 previews) in the Develop module takes 4 seconds before the image is displayed after pressing an arrow key to move (or using the mouse to select an image). When you move to another image, the UI is repainted first (and, i assume, the histogram calculated, etc.), and then the image is displayed on the screen. Moving between the Library and Develop modules also results in about a 4 second delay before the image is displayed. Moving between pictures in the Library module is almost instantaneous.

This level of performance is unacceptable. Doing a copy/paste of settings from one image to another takes longer in the latest Lightroom than in the previous one as the time needed to display the image seems to slow everything down, thus slowing down the entire workflow process.

Another quick test was to press the right arrow key 10 times in succession in the Develop module to move between images. It took Lightroom Classic CC 20 seconds before the UI finally caught up and displayed the desired image. Doing the same in the Library module takes about 3 seconds.

Or, is this just the level of performance to be expected? Was this not tested during the beta process, or just deemed satisfactory by Adobe?

What's the best way to get feedback directly to Adobe on this?

This topic has been closed for replies.

Show previous replies

AmbiOkie

Participant

LR Classic is worse.

----

It crashes regularly.

The "Loading" message appears all the time.

In Develop, images take over 7 - 10 seconds to load on scroll.

In Develop, sometimes the images never load.

Sometimes the "Loading" message never goes away.

Crop tool spazzes out.

---

i7-6800K, Win10, 32GB, NVMe SSD....

This is so ridiculous!

B

bob frost

Inspiring

Have you turned off the GPU and Render previews in parallel under Performance? And have you rendered all your standard previews, or are you leaving LR to do that while you try to do other things?

Bob Frost

N

NHPhoto4

Known Participant

I've tried all those, turning off the GPU makes a marginal improvement. I've tried 1:1 and standard previews, none of which make any difference. It seems as though on opening an image in Develop, there has to be a waiting period before you can start work on it. This varies from a couple of seconds to 5 - 10s. One of the most annoying aspects that I'm experiencing is that real time updates are not being made to the image as adjustments are being made, there is a lag of several seconds, so adjusting exposure/highlights/ shadows becomes a guessing game..until the image updates and you realise it's not what you wanted so then you have another guess..No such problems in ACR, it's a real mystery, to me anyway. I might go back to working in Bridge until it's sorted. I also have ON1 RAW installed. No problems with that either. I want LR to be right though.

N

NHPhoto4

Known Participant

This user would also like to add his two-pennorth -Unbearably slow. I'm half way through a wedding edit and it's like pulling teeth. For example; up to 15 seconds to get an image from Library into Develop, 5-10 seconds to move from one image to the next in Develop module. 5-10 seconds for some adjustments to render into the viewed image, laggy real-time adjustment views such as white and black clipping - occasionally these sliders even take on a life of their own and on trying to catch up they start wildly rolling back and forth of their own accord!. All this is making what should be an enjoyable job a real chore. You're supposed to be being creative whilst trying to work around all these annoying issues? I've messed about with all the various settings as describe here and elsewhere but to no avail, but anyway, surely all these adjustments to various preferences should be considered fine tuning tweaks and not essential for getting any sort of acceptable performance? It should be somewhere in the ball park out of the box? In my opinion, at present LR is not a product that's fit for purpose. In my experience the previous version wasn't much better, I was hoping for a big improvement from this long-awaited update - wrong!. Can't find anywhere to contact Adobe directly about the problem either. Very very frustrated and disappointed.

Win 10 x64. i7 3.50GHz, 32GB DDR3, NVIDIA GTX 1050

C

cambunch

Participant

Another user here with a terrible experience after the update. Had to revert to the 2015 version. My specs are below. I would say most operations took about 3-4 times longer than before the upgrade.

i7-7700k

32GB Ram

nVidia GTX 1060 6GB

Multiple SSDs

stet57

Participant

On my iMac 5K 2015 - i5, 16GB RAM, 256SSD - extremely slow! Scrolling in my library is 0-1FPS on 5k display. Once I move Lightroom window to my secondary screen (Cinema Display 21") scrolling has at least 30FPS!

LR is totally unusable once more than one export is running!

Adobe do to hell! We are photography professionals and all we need is fast, reliable software. This slow peace of crap even on +$2000 computers is shame!!!

Funny point is that browsing RAW files in Bridge is much, much faster than is LR!

nasoj21

Participant

I am also having the same sort of issues. Synchronizing changes to multiple image gets no response sometimes, or an extremely delayed response. Trying to go in and add or change local adjustments almost crashes the program.

If I go back to 2015, can I downgrade my current catologue or do I need to load the one it converted?

michaelh99192563

Participant

During upgrade, a new catalog was created. You should be able to open the old catalog in the old version of LR

For those posting in the last couple of days, have you upgraded to the version that was released since LR was renamed? That version is a bit faster for me...

LindaLMP

Participating Frequently

I may be one of the very few that did not have any issues with speed in the last version of Lightroom. I updated to Lightroom Classic and it is painfully slow. There must be something that is tweaked in the settings. Reviewing and implementing some of the tips found here. Hope they help.

UPDATE: I switched to minimal previews during import and it helped speed things up. I find it much faster to import from memory card to my computer file, then drag/drop into LR. It used to be instant, now there's a delay. It's not as fast as the previous version, but at least I can work again.

J

JamesAllenUK

Participating Frequently

After years of problems with speed in Lightroom, even with a high spec PC, what worked for me - I think - was reducing the number of develop presets I had. Amazingly, when I removed them all Lightroom suddenly became a speed demon both in library and develop modules. I later added a few packs back although I also noticed things weren't quite as fast but I put up with it. With the new Classic update I found the speed was improved but then after using it for a while I got the same old slow down's of the past.

I have just cut down my develop presets and it's flying again!

Not sure if this is just me, but could someone with speed issues try removing all your Develop Presets and seeing if it makes any difference. I'd love to hear if it's just me or if this does make a difference to anyone else.

M

mihai danm44710804

Participant

Hi James!
Thanks for the tip. It seems in my case, as you said, reducing the number of developing presets helps a lot. For a start there is a huge difference. However, after 5-10 minutes everything is slower again. I have to restart Lightroom each 10 minutes to work fast. I think I will disable Map, Book, Slideshow, Print and Web modules as well.
Thank you, James for your time and help!
Cheers,
Mihai.

J

JamesAllenUK

Participating Frequently

Hey a pleasure Mihai. That tip definitely helped me with speed issues with previous versions, however like you I still get slow down after a while. Just came back to this thread to see if anything else had been discovered as right now LR Classic is really dragging it's feet while I'm trying to edit. Really frustrating.

K

kornreich

Participating Frequently

My findings are inline with what puget systems tests showed. Seems like a 6 core i7800 cpu is the sweet spot and also not needing to build smart previews anymore

michaelh99192563

Participant

Well, 7.0.1 just came out. I wonder if that improves things or makes them even worse... giving it a shot...

P

Photosoul

Participant

It seems that the just released update solved problem with performance - at least in my case

P

pixellatious

Participating Frequently

I thought so too, but that only lasted about 10 minutes, then it just got worse and worse as before. Luckily DxO has just released Photolab with local adjustments via masking, or Nik’s u-point technology. So I’ve stopped using the utterly useless LR for now. The strange thing is PS CC 2018 runs extremely well as does Bridge, but LR clearly hates my Ryzen 7. I should note for me the worst perfomance comes from the gradient and brush tool. I can get constant screen blanking, and it can take 90s for the tool to become responsive after an initial adjustment. It works best the first time, but if you go back later it’s deplorable. LR works a charm in grid mode, but it’s the develop module that’s broken for me.

P

Photosoul

Participant

What I found is that I nearly cannot do anything if I start creating 1:1 previews in the background - LR seems like it hanged, it takes about half a minute to wait for any reaction after clicking anything in LR.

B

bob frost

Inspiring

LR Classic now has an option in Performance prefs that allows rendering speed to be doubled. It works! But the side effect is that there are less resources available to do other things at the same time. I avoid trying to do other things while rendering; have a coffee, have lunch, go shopping, render overnight. But if you must do other things, I suggest you turn the Performance improvement OFF. Then you will be back to slower rendering, but have more computer resources left to do other things at the same time.

Bob frost