• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
9

Lightroom Classic CC seems slower than previous Lightroom version it replaced

Explorer ,
Oct 18, 2017 Oct 18, 2017

Copy link to clipboard

Copied

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?

Views

55.5K

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
replies 294 Replies 294
Explorer ,
Oct 23, 2017 Oct 23, 2017

Copy link to clipboard

Copied

Thanks alanterra - Adobe made it easy to get to this forum, but not the other...     I had reported a bug in the past on the other forum, but forgot completely about it, so thanks for the confirmation.

Hate to try to provide constructive criticism if no one that listens has any power to actually change it, so hopefully will see some progress with the feedback site (I did link back to this site and hopefully Adobe will see it).

As a suggestion to others, check the feedback site and if you are encountering any of the reported issues, by all means mark it "me too" and maybe it will get the attention from the right people...

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Oct 23, 2017 Oct 23, 2017

Copy link to clipboard

Copied

Wow - what a day and still LIGHTROOM CLASSIC IS THE PITS!!! (and no progress on getting my post processing backlog worked).  I spent nearly 90 mins online in chat with Adobe Support, regarding the severe slowdown and lag in Lightroom Classic I am experiencing (as are so many others).  First the rep told me "we aren't aware of these problems" (when I told him the community support forum is loaded with complaints of the slowdown).  Second, he had me create a new library catalog, saying the problem was that the conversion when it updated was not successful.  At first we tried this with a test catalog and it seemed to fix the lag and slowness.  So, being assured this will be the fix and I would not experience any further problem (and I even demonstrated as we hooked up with remote live desktop takeover), I finished up the chat and ate dinner and sat down to work on my growing backlog.  It started out with great success.  However, VERY QUICKLY (like 8 pictures later) I started noticing some lag developing in the application and in using the brushes (which is where I had the problem originally).  Well as you would expect, it got worse and within 10 mins, I was experiencing 7-10 sec lag in a brush swipe, and that extended to 15 in some instances.  The program kept freezing and the worst part is I started seeing that infamous spinning ball - UGH!!!!!!!  (so here I sit back online trying to get to Adobe to find out if I can revert to LR 6 (in the photography plan) as I NEVER HAD ANY PROBLEM AND ALWAYS HAD SPEED, SPEED, SPEED IN ALL PRIOR LR VERSIONS.  This is absolutely unacceptable.  To make matters worse, I have gone from number 1 in the question to number 2 four times (not sure how that happens), but I am back to number 1 again.  We'll see what happens.  Bad part is I totally rely on LR for my post processing, so I am really in a pickle with my backlog right now. another UGH!!!!!! (would you believe I just went back to number 2 in line again?  I cannot figure how that could happen.  Maybe they count different in Adobeland.  2, 1, 1, 2 or something like that.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Oct 24, 2017 Oct 24, 2017

Copy link to clipboard

Copied

One more person stuck in the massive slowdown camp.

I wish I'd seen this thread before I updated.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Oct 24, 2017 Oct 24, 2017

Copy link to clipboard

Copied

My experience has been somewhat positive so far.

I have an older XEON 6 Core 3.5ghz 64GB ram Windows 10 Pro setup and I found the following

Import 161 Sony A9 Raw files building 1:1 previews and Smart Previews it took 5:28 in LR CC Classic and 9:41 with LR CC

So thats a pretty good improvement IMHO, I also noticed in the Develop Module images loaded much faster especially when I have the enable GPU acceleration turned on.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Oct 25, 2017 Oct 25, 2017

Copy link to clipboard

Copied

Thanx to everyone testing LR classic performance .. I tried the suggestions you posted .. but If my LR CC 2015 was working quite well, now it has become a nightmare : several seconds of lag between brush strokes or setting change in Develop, LR has become impossible to work with .. OK I have a rather basic machine, but it worked before .. now it doesn't ..

I liked working LR, but do we have to consider alternatives now?

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Contributor ,
Oct 25, 2017 Oct 25, 2017

Copy link to clipboard

Copied

In 2018, no compromise should have to be made. No option to work with lesser quality should have to be set. No user should have to change their way to allow Lightroom to work faster. Adobe has not yet figured out software performance. Whether After Effects or Lightroom, Adobe has many many many years to go before their software performs up to hardware capability. A fully spec'd out PC or Mac should be able to use Lightroom flawlessly. Period.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Oct 25, 2017 Oct 25, 2017

Copy link to clipboard

Copied

Couldn’t agree more. I had this hugeee disappointment as my previous versio wasn’t the fastest performer but I could get the work done but this latest version was really bad very very slow compared to the already slow version.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Oct 25, 2017 Oct 25, 2017

Copy link to clipboard

Copied

LR Classic CC is really a crap release! Performance is medieval at best. And that is on a Mac Pro 5.1 with 48 Gb of RAM, SSD, 6 core 3,46 Ghz Xeon, dual Radeon R9 290X! A couple of years ago I did a test between a PowerMac G4 DP 533 Mhz and a Mac Pro 1.1 2x2 Core running a number of tests in Photoshop of common tasks like unsharp mask, gaussian blur etc. The G4 was running first PS release support ting dual processors fully in OS X, and the Mac Pro the then latest PS-release. Even though the Mac Pro had something like 12x hardware advantage, the times were similar. There were 3 releases between them. Adobes software (I have been told by e former employer of theirs) is a huge gunk of obsolete code, and very little seems to get fixed. And much of the the old code gets recycled in ew software, like Lightroom inherited a lot from Photoshop and CameraRAW, so did the new version of Premiere etc. One thing… neither LR or PS utilises more than 2 cores on a machine with many cores. I do a lot of video and software like DaVinci Resolve 14 and iFFMPEG use pretty much all they can grab, unless you set them up to do otherwise. Adobe products you cant even set up to use more than two...

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Advocate ,
Oct 25, 2017 Oct 25, 2017

Copy link to clipboard

Copied

Strange you should find LR Classic only uses 2 cores! My setup (Win10) uses all 6/12 cores up to about 70% at the same time when rendering previews.

Bob Frost

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Oct 25, 2017 Oct 25, 2017

Copy link to clipboard

Copied

Maybe it's another bug? Previous versions pretty much never used more than 2 cores. The only circumstance I can come up with where LR used more than two, is if I first start at batch of TIFF outputs, and then start a batch of JPEG's. Then LR might use 4 cores.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Oct 25, 2017 Oct 25, 2017

Copy link to clipboard

Copied

Another test: Same for images, same corrections etc, output to 16bit TIFF, 24MP images on a slower machine with 20Gb or Ram and i3 3225 @ 3,33 Ghz CPU, SSD and Radeon 7970 GHz Ed. Lightroom CC: 64 seconds, Lightroom Classic CC 3 minutes 46 seconds. And then Lightroom CC used 2 cores while Lightroom Classic CC switched back and forth between 1 core and 3,5 cores (85% and 350% CPU usage). lightroom Classic CC uses loooooads of disc-cache by the way! Probably a huge memory-problem that causes this.

While setting up this test, I tried switching to Develop-module in both versions, and Classic CC shows a black screen for 3-4 seconds and after running the test I tried painting masks in Classic CC… the beachball all the time.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Oct 25, 2017 Oct 25, 2017

Copy link to clipboard

Copied

Thank god it's not just me. I have a new AMD based Ryzen 7 1700X system, with 32GB memory, 1TB SSD drives, Nvidia GTX1080Ti, and the performance of LR Classic CC is appalling, it's unusable. I even tried the trick to limit the number of threads to cores+1 in a .lua file, but it only helped a tiny bit. I'm getting huge freezes, screen going black for up to 20s, even taking 10s to switch to new photo in develop module, sliders unresponsive for up to 30s. It's unusable. LR CC 6 was much much faster. I now have to go to trouble of uninstalling to go back to LR CC 6 or just stop using it and move to C1 and DPP. Turning off the graphics acceleration helped a little with screen blacking out, but nothing else. I can't believe how this was pushed out as ready. It's like a pre-pre-alpha.

I do have these issues with any other program including PS CC 2018

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Oct 25, 2017 Oct 25, 2017

Copy link to clipboard

Copied

I've the same issues stated before.
I've catalogs with 30k+ images and I've noticed LR CC Classic tends to recreate all the standard previews for the new catalog everytime you access a folder.
The slowdowns could depends on this process, which is CPU time consuming.
Anyway, I've faced a lot of black preview when switching between images or between Libray and Develop module.
Plus it happens when using brush for selective modifies and spot removal: it stops responding for 3-4 seconds.
Closing LR CC Classic sometimes, after half an hour improve the performance a bit.
Anyway is far from anything that can be called fast and efficient.
I've a i7 3820 3.6Ghz (quad core), 32GB DDR3, 256GB SSD, Windows 10.
All the catalogs and previews are on the SSD, images on a separate hard drive.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Contributor ,
Oct 25, 2017 Oct 25, 2017

Copy link to clipboard

Copied

Upon the advice of a previous poster, I called Adobe and spent quite a bit of time with him. He helped me reinstall LR2015 which probably saved me some time. The changes he made in Classic didn't help, so I am (happily) back in LR 2015. I had made quite a few changes to my catalog over the four or five days while in Classic, so I had to resync a lot of my folders in 2015.

I will delete Classic, then install it clean without updating my main catalog.  I can experiment with a dummy catalog before committing to it when they release a speed/bug fix.

The tech said I would need to install and use LR Classic to be able to read Nikon D850 raw files. It's on order.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Oct 26, 2017 Oct 26, 2017

Copy link to clipboard

Copied

I am using an iMac with a Intel Core i7 @ 3,4 GHz with 32 GB RAM and a NVIDIA GeForce GTX 680MX 2048 MB. In comparison to Lightroom CC (the old one) is the "new", Lightroom CC Classic, ridiculously slow! What have you done to this piece of software. After working on a single image and about 10 steps, the software starts to think about every step. Please do your homework and update the software! I have installed the "old", one again!

Modellname: iMa

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Oct 26, 2017 Oct 26, 2017

Copy link to clipboard

Copied

After editing multiple images on my iMac 27 i7, Lightroom Classic CC slows down considerably. Importing images (copies) doesn't happen any faster than with the previous version Lightroom 2015 - Adobe should be ashamed! They had promised speed boosts! Where are they?

TypoFreak on Mac

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Oct 26, 2017 Oct 26, 2017

Copy link to clipboard

Copied

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.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Advocate ,
Oct 27, 2017 Oct 27, 2017

Copy link to clipboard

Copied

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

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Advocate ,
Oct 27, 2017 Oct 27, 2017

Copy link to clipboard

Copied

Here is an analysis of the speed difference between the old LR CC (2015) and the updated LR Classic CC -

https://www.pugetsystems.com/labs/articles/Lightroom-Classic-CC-is-it-faster-than-CC-2015-1065/

Bob Frost

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Oct 27, 2017 Oct 27, 2017

Copy link to clipboard

Copied

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

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Oct 27, 2017 Oct 27, 2017

Copy link to clipboard

Copied

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

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Oct 28, 2017 Oct 28, 2017

Copy link to clipboard

Copied

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.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Oct 27, 2017 Oct 27, 2017

Copy link to clipboard

Copied

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

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Oct 27, 2017 Oct 27, 2017

Copy link to clipboard

Copied

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.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Nov 27, 2017 Nov 27, 2017

Copy link to clipboard

Copied

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.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines