No worries.  Figured there was a magic "work faster" checkbox that was hiding somewhere that I missed...  ... View more

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... ... View more

Hi dnilp - do you happen to know what it is that they had you change? ... View more

I have no idea if Adobe reads these forum messages or not, but when I did a search to report bugs in Lightroom, I was pointed to another forum that mabe they read? https://feedback.photoshop.com/photoshop_family So, not sure how this forum and the other forum differs, but did see Adobe respond to posts in the other forum, so I reported the develop module performance degradation that I experienced. FYI... ... View more

Here is my system configuration: Windows 10 i7-5960x CPU - 8 core, 16 threads 32GB RAM SSDs for boot drive, application, pictures, cache, catalog, etc. Nvidia GTX-1080 (8GB) display resolution: 3840x2160 (4K) This machine should hum with Lightroom... ... View more

Sorry for the long post!  Feel free to skip to the graphs...  🙂 I appreciate all the comments and feedback from everyone and glad (not the right word) to see that others are also experiencing performance problems as I am.  It sounds like there is still much work for Adobe to do to address the user experience when it comes to performance, but it also sounds like they're trying, so hopefully they will continue to focus more time and resources on this issue. I still stand by my initial comments that my first experience with Lightroom Classic CC was AWFUL compared to Lightroom CC, when my expectations were that the new app should be a noticeable improvement over the old app.  I saw a level of performance degradation that just surprised the heck out of me, so was really disappointed in the Lightroom app update. While my subjective experience was negative, I decided to step back yesterday and try to perform some objective "benchmarks" where I repeat a number of steps to try to quantify what I am seeing when I use Lightroom.  I was shocked to find that when I performed these tests, I actually found Lightroom Classic CC to perform better at some tasks than Lightroom CC 2015 - when I saw "shocked," I mean that this was totally contrary to my initial experience that prompted me to start this thread.  That being said, I did experience a huge performance degradation when actually doing a series of steps to emulate a common workflow that I perform, with a degradation by as much as 50% with the new Lightroom Classic CC over Lightroom CC 2015, which I can see would make using Lightroom Classic CC a huge step backwards - but, I digress... For my test, I tried to emulate my initial experience of converting my existing catalog with Lightroom Classic CC, importing some images, and working with the images. I performed a series of steps with both a brand new empty catalog, and the same steps with my current catalog, using both Lightroom CC 2015 and Lightroom Classic CC.  Each set of steps involves performing the following operations: - importing and building previews.  For this test, I used 70 images from a Nikon D500, which has 20mp images, from RAW uncompressed 14-bit files - the actual files shouldn't matter as what is important is the relative performance in each scenario, and your mileage will vary.  For this action, I performed a drag/drop of the image folders into the Library module window. - after the import is complete, I selected the first image in the Library module, set the image view to be Fit, and then stepped through the images.  While normally one wouldn't just step quickly from one picture to another, measuring the amount of time to step from one picture to another is problematic as there is too much error related to reaction time, so expanding the test set provides a better measure of performance.  I guess one could take the time and divide it by the number of pictures to get the per-picture time, if one was so inclined.  When moving between images, I moved the next image, then waited until the UI completely finished. - I then performed the previous step in the develop module.  In this module, I closed each of the develop tabs as the contents of the open tabs are calculated/drawn/whatever each time the image is displayed, so this affects the performance of displaying an image. I also did not apply any settings changes to the images. When moving between images, I moved the next image, then waited until the UI completely finished - when in the develop module, this seems to be when the "Auto" button in the Tone section is available and not "greyed out." - I then performed the previous step again, but this time I opened the Basic, Detail, and Lens Correction tabs (ones that I commonly use when editing), with the rest of the tabs collapsed/closed.  Again, When moving between images, I moved the next image, then waited until the UI completely finished - when in the develop module, this seems to be when the "Auto" button in the Tone section is available and not "greyed out." - Since I had seen comments from users that said exporting was supposed to possibly be faster in the new Lightroom Classic CC, I threw in an export of the set of images to JPG images.  For the export, I stayed in the Develop module, selected the first image, did a Ctrl-A select all, then File->Export. new empty catalog... Lightroom CC 2015 import & build smart previews and 1:1 previews: 3:22 library nav: ~60 sec develop nav: 1:43  all tabs closed develop nav: 2:43.  Basic, Detail, Lens Corrections open.  rest collapsed export to JPG: 60 sec LR Classic CC: import & build smart previews and 1:1 previews: 1:47 library nav: ~40 sec develop nav: 1:03  all tabs closed develop nav: 1:53.  Basic, Detail, Lens Corrections open.  rest collapsed export to jpg:  crashed.  "bad_module_info has stopped working" export to jpg: 55 sec (All times, lower is better) existing catalog... LR CC 2015: import & build smart previews and 1:1 previews: 3:38 library nav: 50 sec develop nav: 1:28 sec  all tabs closed develop nav: 2:06   Basic, Detail, Lens Corrections open.  rest collapsed export to JPG: 1:01 LR Classic CC: import & build smart previews and 1:1 previews: 1:47 library nav: ~55 sec develop nav: 1:05 sec  all tabs closed develop nav: 1:58  Basic, Detail, Lens Corrections open.  rest collapsed export to jpg:  53 sec (All times, lower is better) Looking at the above measured times, it appears that Lightroom Classic CC IS faster (or should be faster) for tasks such as importing and navigating through images.  Again, that was not my initial impression, so these results surprised me.  These numbers do not directly reflect what I first experienced after installing Lightroom Classic CC, and Lightroom Classic CC did seem to perform better after exiting and restarting the app, so not sure what was up with that.  Also, the performance difference between working with the empty catalog versus my existing catalog was negligible (so that didn't account for my initial awful experience with Lightroom Classic CC). Ok, given that the above results encouraged me in expecting LR Classic CC should be faster than LR CC 2015, I decided to do real work and actually try processing my set of 70 images and see what happened... I went ahead and performed some common edit adjustment operations on my images including tweaking these settings: - increase exposure - increase contrast - lower highlights - increase shadows - lower black level - increase clarity - increase vibrance - increase saturation - increase the sharpen mask - increase sharpening - increase Luminance noise reduction - Remove chromatic aberration - Enable profile corrections I did this to the first image in the develop module, then synced all the settings through the set to apply the changes to all.  I then waited a short time while the settings were made. I then went back to the first image in the set and performed the above task of stepping through the images displayed in the Develop module...  and Bingo!   Lightroom CC 2015 was more than twice as fast as Lightroom Classic CC!  While the percentage varied from my very first experience with the new update, this was closer to the performance degradation that I initially experienced. existing catalog... LR CC 2015: develop nav with settings applied:  3:01  (versus 2:06 with no settings applied) LR Classic CC: develop nav with settings applied:  6:22  (versus 1:58 with no settings applied) (All times, lower is better) I expected the times to be slower with settings applied and the develop tabs open, and this is what the measurements show.  These results show that Lightroom CC 2015 is impacted by edit settings about 50% (versus when they are not applied) when it has to do the extra work with factoring in setting changes, but for some reason Lightroom Classic CC is impacted by roughly 225%!  For a performance-focused release of Lightroom, this is not what I would expect.  If you do the calculations here, when moving between images in the Develop module with settings applied, Lightroom CC 2015 averages roughly 2.59 seconds to move between images, and the new Lightroom Classic CC averages roughly 5.46 seconds (this is before the UI stops updating itself and LR finishes processing the image for display).  I also found some pictures displayed faster than others, and also that the further I moved through my image set in the develop module with Lightroom Classic CC, the longer it seemed to take (so, degradation over time). Granted, no one normally would step through one photo after another, BUT what this shows is that after editing an image and moving on to the next image, the workflow takes a huge performance hit while the user sits there waiting for Lightroom to finish updating the display before the user can begin the editing process.  While this may be no big deal working on a few pictures, factoring this in for working with a hundred pictures or more means that the user is idle more than the computer is, which should NEVER be the case. So, this should at least show, objectively, that Adobe has work to be done in the Develop module of Lightroom Classic CC to help improve workflow performance, and can actually represent a huge step backwards from Lightroom CC 2015... ... View more

ok, I can see that perspective - thanks.  Appreciate your insight! ... View more

"One note is that 1:1 previews do NOT do anything for performance in the Develop module." I will give that Adobe is not 100% clear on this, or perhaps not explicit as to what happens with the Develop module.  From the performance tips below, it seems to imply that only standard and 1:1 previews are used when viewing or working with images, and any other preview settings (embedded, etc) requires processing in the background to automatically generate the 1:1 previews.  For the unclear part, the reference below to using 1:1 previews helping the Library module leaves out what happens with the Develop module - is the Library module just an example, or a special case?  Adobe doesn't say, but it seems like it's just being used as an example (otherwise, when you do a 1:1 zoom, the preview would have to be generated at that time, affecting performance for viewing the image). I am fine with having a slower import time (can step away from the computer) as long as my workflow is optimized, so 1:1 previews seem to be the recommended option to select at the time of import. Adobe doesn't say what happens in the Display module.  The references to "work with photos" below implies the Develop module to me - other than viewing and culling, what real "work" does anyone do in the Library module?  All real photo editing work is done in the Develop module... from here: https://helpx.adobe.com/lightroom/kb/optimize-performance-lightroom.html Lightroom uses previews to display photo thumbnails in the Grid view, the Loupe view, and in the Develop, Slideshow, Print, and Web modules. ... These previews are a 100% view of actual pixels and, like Standard previews, the Camera Raw engine processes them. When Lightroom generates 1:1 previews, it also generates minimal and standard previews, so all three are available to the program as needed. Because so much data is being processed, 1:1 previews can take a significant amount of time to create. Any time you zoom to 1:1 or higher in the Library module, Lightroom uses 1:1 previews. To display and work with photos, Lightroom requires a standard or 1:1 preview, depending on the task. If, upon import, you only tell Lightroom to generate Minimal or Embedded previews, Lightroom creates Standard and 1:1 previews automatically as you’re working in the application. This process hinders performance. To increase your productivity and reduce this disruption, manage when and how you render your 1:1 previews. Render them on import, or set aside time to render them manually. To render 1:1 previews on import, use the File Handling panel of the import window. Choose Render Previews > 1:1. Although generating high-quality, 1:1 previews on import slows the import process, it makes Lightroom more responsive when you start to work in the Library module. An alternative, if you want a speedier import process, is to render minimal or standard previews on import. Then, at any time, select multiple photos in the Grid view of the Library module and choose Library > Previews > Render 1:1 Previews. Let Lightroom process the images before you start to work on them. ... View more

Mrjackson - from the creative cloud app there is a drop-down for the app that lets you download previous versions.  You can install the previous version along with the new version, so you can have both versions on the system. ... View more

Good question.  Yes, I had “build smart previews” checked on at the time of import. ... View more

Thanks 99jon - except, would that only affect the import performance when building previews? I know that building previews is supposed to be faster in LR Classic CC, but haven't tested against LR CC 2015. I'll give it a try at least! ... View more

Thanks for the tip.  I checked the Smart Previews preference setting and it was off.  Unfortunately, I turned it on and saw little to no difference in performance. I always built Smart Previews in LR CC 2015, but didn't see a setting for turning on/off the use of smart previews as a preference setting ... View more

Thanks for the feedback.  When you say that "camera previews appear almost instantaneously," is that in the develop module? I went ahead and reinstalled Lightroom CC 2015 (the previous release) and moving between images in the develop module is almost instantaneous.  So, something seems to be broken (or changed) in the new Lightroom Classic CC version... I don't usually jump along the filmstrip, but just used that as a example to show how the performance degradation can be compounded when doing multiple actions. For my workflow, I'll import the images and have 1:1 previews generated at time of import (I use a sidecar XMP).  After I select the images to work on, I'll edit an image and then either sync or copy/paste settings from one image to another.  While Lightroom CC wasn't a speed demon (and seemed to get slower release after release), Lightroom Classic CC seems to pale by comparison. It also looks like exiting LR Classic CC and restarting it helped a bit as the time has gone down from 4 seconds to 2-3, but still seems slower than LR 2015 ... View more