Skip to main content
Participating Frequently
October 18, 2017
Question

Lightroom Classic CC seems slower than previous Lightroom version it replaced

  • 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.

    97 replies

    Participant
    November 13, 2017

    Slow switching between photos in the Dev module affects users with monitors higher than full HD (1200+ pixels vertical )

    if Sharping section visible by default, it takes a lot of time

    to render sharping preview thumbnail (it is not cached on the disk (but cached in memory, BTW))

    ex: if You click tab and have no controls displayed in the dev module ->You can see that switching is immediate.

    Great, than, you can work it around until it is fixed by Adobe:

    just close Sharping section and display when You need it. switching is near to immediate.
    (You hardly need it displayed all the time)

    I think Adobe should submit performance bugs that are not visible for Adobe QA,

    but visible to huge number of customers :


    for the issue in this post (slow switching between photos in the Dev module)

    and two issues (spelling and performance) reported in my previous post

    Participant
    November 13, 2017

    I found solution for Slow previews generation problem (4-8 times slower)


    In the properties there is a performance option that degrades performance:

    Generate previews in "paralle"

    "Paralle" will make it 4-8 times slower, instead of faster.

    turned on by default on CC Classic.

    It has a side effect. when You turn it off You can't work in parallel with previews generation.
    I think it is caused by lower priority for the generation threads.

    But, If You need 80minutes for efficient work with generated previews, and generation is much slower than Your process of review,
    that it is reasonable to wait 10-20 minutes with turned this option off, instead of troublesome 80 minutes.

    As suggestions for a fix for Adobe: consider user interaction in the application to be subject to lower down priority for the threads,
    while user is not active, make priority higher.
    If Application is on top (means no other applications really used and require immediate redraw),
    optionally LR could raise priority near to real-time ( You still don't use even 70% of CPU when app is active)


    Alternatively there could be "speed slider" that is easier to explain to user.
    in this case user could choose between render speed and input lags.
    there could be preview speed in one side of slider and user response on another. (kind of preview generation booster)

    skyrunr
    Inspiring
    November 13, 2017

    Nice find Tim, I'm staying on the 2015 version for at least a few months.  If they are going to have their users test the software then we're going to have to take that approach.  It is nice to be working again, and a real wake-up call.

    The best DAM (and ANY document/file manager/viewer) I've ever had was on Windows 95 called PC Tools for Windows.  Symantic bought them out and killed the product.  It gave Windows 95 some features Windows 10 still lacks, and that was back in the days of Wordperfect v Word and Excel versus Qquatro!

    antard
    Participant
    November 12, 2017

    I literally just typed into google to see if anyone else thought that the new Lightroom Classic is slow. Stunned by the results and clearly its not just me.

    My own experience has been awful so far, that I thought my mac might have mad a virus but that is not the case.

    So far when scrolling through Develop mode it lags and bugs out. taking 5-10 seconds to catch up on itself. I thought it was supposed to be fast, never had this problem before.

    Oh and the spec of My imac.

    Processor:3.4 GHz Intel Core i5

    Memory: 32GB 1600 MHz DDR3

    Graphics:NVIDIA GeForce GTX 780M 4 GB

    As a wedding photographer I have processed thousands of photos before without problem, this version is awful! You are not alone in knowing that Lightroom classic is slow, very disappointed considering they said it was faster. What a major boo boo. Sort it out Adobe!!

    Known Participant
    November 11, 2017

    I see the same issues. Not at all promised performance improvements. It got worse on my Mac with GPU enabled in particular in Develop module.

    skyrunr
    Inspiring
    November 8, 2017

    Hey everyone,

    I'm done being their unpaid beta tester.  I reverted back to 2015.  I recommend un-installing "Adobe Photoshop Lightroom Classic Creative Cloud" before reverting.  The CC is really just a billing scheme.  (Don't get me started on Photoshop, Elements, and Lightroom inconsistent naming.  I have them all installed on my test machine and it is rather hilarious seeing them side by side.  I worked for a national software company and KNOW what it is like to spend hours or days on things that should be very simple.) 

    I went to quit creative cloud and there was a $30 fee for half the remainder of my CONTRACT!  I don't remember this, and this is also why I don't like to pay things monthly!  I would much rather pay my bill in one shot.  It is clearer what you are buyingHowever, I got two free months, so I'll use that to see if they fix Classic by then.

    You can revert within the Adobe Creative Cloud application by clicking on the tiny down arrow by the install.  Even when you install the 2015 version there it has to update when that is done.  I wanted to run both to see if APLRCCC gets any updates, but that was a huge mess as the executables are both lightroom.exe and APLRCCC takes back over.  My catalog folders are a complete mess because of the changed folder structure and I have to dig around and delete all of those cache folders.   Don't forget to backup your presets if you don't have a automatic versioning backup running like BackBlaze.

    PS  Elements 2018 smartfix is pretty awesome compared to LR's tone and wb madness.  I still prefer pegging levels in photoshop, but my D500 is dialed in so well I don't need that level of adjustment anymore.  It has the Camera Raw interface, and I sort of like the light table more, but I didn't at first.

    good luck!

    Participating Frequently
    November 8, 2017

    Majority of us with problems have I think, tried going through nearly everything we can think of.

    So by now we know that it doesn't seem to be anything any of us can fix.  However, the majority of other users 'appear' to be fine with the update.

    I know it's a long shot, but it kind of points to the fact that we all have something in common, a hardware or software commonality that's causing this problem, because well it can't really be random, can it?!?

    Can we all post our specs and list main software here to see if we have anything in common:

    OS:

    • Win10 64bit - all latest updates

    Other software:

    • MS Office 2013 (pro)
    • Adobe CC full suite all updated
    • Articulate 360
    • Sophos Antivirus

    Hardware (Dell Precision 5510):

    • Intel i7 Skylake 6700HQ 2.6Ghz (seems to be capped at 30% 0.78Ghz even when I'm doing CPU stress testing!)
    • 32GB DDR
    • SSD 1TB
    • Onboard intel 530HD
    • Nvidia M1000M Quadro display adaptor

    Could you also check your CPU speed too please.  If you don't know how to do this follow these instructions:

    This should work regardless of Windows OS version:

    1. press Ctrl + Alt + Delete keys on keyboard - then select Task Manager from the screen
    2. * or go to the start menu and type Task Manager, then select Task Manager
    3. The Task Manager window should pop-up.
    4. From the tabs along the top of the window select the Performance tab
    5. It should display some system information on this screen and should be monitoring performance in real-time.
    6. If you have the option (dependent on OS) ensure the CPU is selected.  It should state the overall CPU speed and current utilisation in a percentage and actual clock speed, for example mine was 2.6Ghz, utilisation was at 30% 0.78Ghz. 
    7. Keep this window open and start up LR or something else and do something taxing and keep an eye on the CPU utilisation, it should go up, even to 100% or close to momentarily and keep going up and down while your working away. 

    The reason I ask this is that I believe mine could be the issue, or at least partly the issue.  I've run 4 different stress tests, Prime 95, SisoftSandra, Cinebench and PCMark all of which should max out the CPU to 100% for the duration of the test, but mine is stuck at 30% 0.78Ghz for some reason.

    Participant
    November 8, 2017

    It’s real simple. Regardless of platform, we were all satisfied with the performance of LR. The day I switched to Classic, my performance dropped dramatically.

    A proven tool turned into a tool that affects my business.

    They’ve had a couple weeks to fix this. I can’t help but believe this is deliberate on Adobe’s part - to drive us to the multi-platform LR - with less features. Why would they want to support two products in the same market?

    RickWLCCC
    Participating Frequently
    November 8, 2017

    PhilD - The writing is on the wall I'm afraid.  As soon as I saw 2- versions offered, I knew the end was near for the original.  From a business standpoint, there's no practical reason to offer 2 unless you were trying to phase people into the new.  Overall, this might be a good thing.  I'm thankful for Adobe, as I use/teach all their software.  But, it's at a point in which real competition is stifled.  One of the best things about running your own business is not being tied to anything.  Lately, I've felt very "tied" to Adobe. 

    FYI - I've done the same work as you describe [sports].  Albeit, you probably already know this, turn off the high speed shooting option on the camera.  Once I did that, my ability to capture the "right" shot increased incredibly.  Shooting 10 frames a second became a joke and never really gave me what I thought it would.  Good luck

    RickWLCCC
    Participating Frequently
    November 7, 2017

    I've read through a lot of this thread.  I noticed an immediate slow down after upgrading.  I've been a subscriber for 4 years and update as each version is released.  I've noticed slow downs moving from tab to tab as well as using the individual tools.  I have a late model iMac with 30+ gigs of RAM.  My external drives are all Thunderbolt.  I see the "apple-pinwheel" more now than I have in 8 years of using PS on a Mac.  I do not see this as a "preference" or "setting" issue.

    Participating Frequently
    November 7, 2017

    So just to clarify my attempts to resolve this issue:

    1. new catalog
    2. import old catalog
    3. drivers - display/motherboard/CPU etc
    4. windows updates
    5. uninstall and complete Adobe system clean including registry and temporary files clean up.
    6. adjusting preferences in LR
    7. trying LR 2015 CC
    8. disconnecting other monitors  - I really questions her on this, but played along anyway, didn't make a difference whether I use one or 3 monitors.

    Nothing worked so far.  So from a fresh install on a new machine back in July, LR 2015 CC ran stupendously fast.  For example, HDR merges were done instantly.  By instantly I do literally mean instantly to the point I'd check twice to make it's actually done as it was so quick it seemed as if it hadn't done anything.  Importing 8GB took mere seconds, organising images in library and editing in develop modes were very smooth and quick.

    Now it takes 3-5mins to import around 8GB, exporting is also a painful wait.  Moving around and doing anything in any of the modes is terribly laggy.  For example, applying any changes such as altering exposure it can take 5-10seconds to the see the result on screen.  It's like I'm sending instructions down a long chain of command and the elves inside the computer are overworked and tired.

    I also sent the link to this thread to Adobe and the support tech said she'd alert her colleagues to it.

    My system spec:

    i7 (quad-core, 8 logical processors), 32GB RAM, 1TB SSD (64% free capacity), Quaro M1000M card, intel HD 530 as well,

    Community Expert
    November 7, 2017

    NasMaximus  wrote

    ... Importing 8GB took mere seconds, organising images in library and editing in develop modes were very smooth and quick.

    Now it takes 3-5mins to import around 8GB, exporting is also a painful wait. 

    Seconds for 8GB? Typical high speed memory cards clock around 80MB/s. If you have a good card reader (so not using a USB2 connection to a camera), you might be able to get that. At that speed, 8GB takes 100 seconds just to copy the files! If you use a direct camera connection or a USB 2 reader, you won't even get 80 MB/s and your copy will take twice as long. There are your 3 minutes. While something is clearly wrong with Lightroom, there are physical limits to what you can do on import. If you spend a lot of money on cards, you can get faster ones especially if you use compact flash memory but if you don't have a good reader you will never get anywhere near GB/s speeds.  Remember that even fast, modern SSD drives are only doing 500 MB/s or so. No way a memory card is near that.

    Participating Frequently
    November 7, 2017

    I use a USB3 reader on a USB3 port and UDMA CF cards.  There's nothing I can do the prove this at the moment obviously due to the problem I'm having, but I can tell you now it took less than 3mintues!  Seconds was probably exaggerating on my part, but realistically much less than 3mins I can tell you that much.

    skyrunr
    Inspiring
    November 7, 2017

    Everyone; if you haven't done so (count is only 40,) please view the original post and click on "I have this question too."  This might help it get more attention from Adobe.  Someone spent two hours with Adobe support and got nowhere, as I suspected would happen.  Having worked in third level technical support and escalations for MANY years, I have no patience for modern technical support. 

    I probably won't replace Photoshop, may even go back to CS6 with DNG's, and I'm testing every other DAM out there.  All we can continue to do is be squeaky wheels and watch for an update.  They've pretty much admitted that the core engine is aging and limited...

    Inspiring
    November 7, 2017

    skyrunr,

    I am limping along with LR Classic 7.01 on a PC. The Develop module is working fine, but importing is a pain. I spent a couple of hours with Adobe tech support, too. He took control of my computer and did a few tweaks, but importing was still very slow. I need LR Classic to work to be able to import Nikon D850 files. ACR in PS reads them, but not LR 2015. That doesn't help me cataloging my files in LR however.

    I bought OnOne based on their claims of blazing fast previews...not so much. I typically use LR for importing, which creates all of the xmp files. When I go to their program to cull, I end up with remnant xmp files they don't delete when the main file gets deleted. I called their tech support and they acknowledged it wouldn't delete the xmp files. OnOne might work fine if you import them there first, cull, then import the keepers into Lightroom.

    I also bought Photo Mechanic specifically to speed up culling. Actually that works fine. Some people like it for their front end, but it's not well integrated with Photoshop, at least the way I work. After deleting files in Photo Mechanic, all I had to do was sync the folder in LR.

    Good luck with your quest.

    skyrunr
    Inspiring
    November 7, 2017

    LRCCv6 isn't un-installed automatically (a preferred glitch?) on Windows, and all 5GB of it was still on my machine.  You should be able to create a shortcut to the old lightroom.exe (or DMG on mac) executable, jump right back over to LRCC-V6 along with the prior version of you catalogs before they were converted re-written as catalogname-copy.  Unfortunately, I just got a new camera and did a ton of non-editing work in one of my master catalogs.  It would be a little too painful for me to revert.

    Participating Frequently
    November 6, 2017

    So after my 2hr call to Adobe support the other day I'm nowhere nearer to a solution.

    Drivers checked, LR uninstall, Adobe clean-up, and LR reinstall.  Tried LR CC 2015 (slow now too).  She went through a few more settings, but nothing has helped. Last thing she asked me to try before I hung up was to import new catalogue which hasn't made a difference.

    I'd already tried a completely new catalog.

    Not sure what else to try.

    Inspiring
    November 6, 2017

    You haven't mentioned creating a new Preferences file? That often solves problems. Rename any old prefs files, just in case LR still cannibalises them. You could also try disabling any Plugins that you have installed.

    Bob F