Skip to main content
Known Participant
September 25, 2017
Question

Performance - From a Computer Science Point of View

  • September 25, 2017
  • 74 replies
  • 2259 views

Like others, I am having a frustrating time with Lightroom editing photos from a performance standpoint.

My workflow typically has me creating a new catalog for a particular photo shoot, importing the (RAW) photos and applying a custom preset on import and then editing the photos one by one in the Develop Module.

After editing a number of photos (say, 10-25) the performance of Lightroom degrades significantly and I have to exit Lightroom and re-start it to continue editing (and continue to do so until I have completed my editing).

I have done significant research into Lightroom performance issues and have tried all of the suggestions and all possible permutations thereof to no avail.  I have also profiled Lightroom with a number of Windows development tools to take a look at it's I/O, threads, memory, etc. and nothing specifically stands out.

I do understand that Lightroom stores it's editing changes (whether via a preset or manually) in a SQLite database and then applies these changes to a photo in 'real-time' to render what you see on the screen.  That leads me to believe that the program is having a difficult time querying the database and applying the changes in 'real-time'... it is almost like there is a 'leak' as one moves from one photo to the next.

Edit: I took a quick look at the Lightroom .lcat file which is actually a SQLite database.  In it, I found 102 tables.  Still looking at the relationships between these tables.

All of the suggestions to add faster disks, larger caches, build previews, etc. are all masking the real culprit which I believe is an internal data structure, database, etc. issue.  My 'evidence' for this is that exiting and re-invoking Lightroom will always provide me great performance until I reach 10-25 photos and then I have to 'rinse and repeat'.

What I would like to know from the Lightroom software development team is whether there is a way for uses to 'peek' inside the program to know what is actually going on from an operating system and computer science perspective (open files, memory allocation, threads, locks, etc.).  I would assume that the Lightroom software development team knows exactly what is going on as the program is likely instrumented.  Knowing what it is that is causing Lightroom to gradually degrade its performance will help users understand how our behavior might need to change when using Lightroom to improve our experience (like perhaps not/not applying presets to hundreds of photos at once rather, do so as you edit one photo at a time).

I do love Photoshop and Lightroom and recommend the products to everyone that ask me for advice but I also believe that Lightroom's performance issues are serious and need to be addressed.

Thank you for your consideration

This topic has been closed for replies.

74 replies

Known Participant
November 1, 2017
Assaf,

I don ́t see any speed decrease over time in LR Classic. Or maybe it ́s so little that I don ́t notice it. But I know that I had a slowdown in LR6 and a restart solved the problem. But I had to be rather careful to notice it: After mabye 10 minutes, the sliders` responsiveness on screen (or let ́s call it the image redraw) wasn ́t as smooth as at the beginning.
Assaf Frank
Participating Frequently
November 1, 2017
Do you mean your CORE I9-7900X 10 Cores replaced your old i7-7700K 4 Cores and both suffered from performance degradation in the same way? or both had no performance degradation?
chrisc25335006
Participating Frequently
November 1, 2017
Well my 7900k replaced a four core 7700k which was exactly the same.
Assaf Frank
Participating Frequently
November 1, 2017
it might be the core count, anything above 6 might be an issue?
Assaf Frank
Participating Frequently
November 1, 2017
Very interesting, so your Lightroom doesn't get slower over time in the develop module? and you don't see any performance improvement after restart?
Known Participant
November 1, 2017
I ́ve tried your procedure with 30 Raw files from a 7D MK2. Export takes 12 sec. each and every time. No speed degradation here. No restart of LR after exports.
Win 10 (Anniversary Update), I7-5930K (6-core@4ghz); GTX 970 (Driver 376.33); 32GB RAM; LR Classic 7.01.
CPU always at 100%
Assaf Frank
Participating Frequently
November 1, 2017
Hi Guys, I have first alerted Adobe on this slowdown a year ago, on this thread which was largely ignored. it was related to export speed being double the time after working on images compared to export the same batch after a restart.

https://feedback.photoshop.com/photoshop_family/topics/lightroom-image-export-is-much-faster-after-r...

I have also linked the performance degradation in export results to the general slowdown in image editing. its all stem from the same issue to my analysis and by doing simple export benchmark which I will outline below we can give Adobe simple performance data. Adobe can try and replicate it very easily in their high-end CPU test machine.

here are the steps.

1. select 30 images for export as full size add them to a collection called '30 images export speed test'
2. Open the task manager and put it on the CPU graphs
3. Restart Lightroom
3. start the export and time it using your stopwatch on your phone.
4. you will notice the CPU shoots up to 100% on the first export
5. do a print screen of it if you want to post it here
6. once the 30 images have finished start the exact export again, without restarting Lightroom
7. look the CPU graph and you will notice no more 100%, Lightroom is now slower.
8. time it and take a print screen of the CPU graph if you wish to share it.
9. do it again, and time it and see if it's getting even slower
10. post your results here, with the OS, CPU/GPU type and No of Cores and type of Raw files

one big question is there anyone out there that the results are consistent with no performance degradation I would love to know their spec! 

here are my results for
30 raw files of phase one IIQ 280 80MP
Windows 10, i7 5960X 8 Cores,Nvidia 980Ti, 64GB RAM

export times Lightroom Classic CC 7.0.1 in minutes per run in order
1. 2:31  
2. 3:17
3. 3:56
4. 4:35
5. 5.10

clear performance decrease...

here are the CPU graphs 
1. first run CPU maxed to 100% most of the time 


2. second export CPU less busy export is slower


3. third export CPU even less busy and export is even slower

4. forth export even slower, I the screenshot you got the idea ...

Here are the capture one 10.2 times for the same 30 images in minutes
1. 1:17 
2. 1.16
3. 1.17
4. 1.16
5. 1.17

here is capture once CPU graph which you can see there is plenty of CPU to keep working on images while the export is running at consistent speed, no performance degradation.


Capture one puts Adobe to shame.
chrisc25335006
Participating Frequently
November 1, 2017
I have just reinstalled a fresh version of Lightroom Classic on a fresh Windows 10 installation of the Fall Update. I have a high end system with NVMe SSDs and a GTX 1080Ti with a 20 core 7900X Processor. I have exactly the same problems as described here, a slowing down after a while. I am appalled at the reaction I get from Adobe, which usually is “disable the GPU” or “we can’t test every system”. To be clear this is a fresh installation with no other Software installed except BitDefender 2018 - is this the problem?

I’ve now let my subscription lapse and gone over to Capture One, which performs fine, but I will follow progress and perhaps come back to Adobe if the issues ever get sorted. Frankly though after years of the software going downhill performance wise, and the attitude of Adobe - I am not holding out much hope!
fingham1Author
Known Participant
November 1, 2017
Just read Joel's latest comments.  I have exchanged emails with Joel and I can attest to the hardships he is having with Lightroom Classic.  I too, have had issues with the product (although, I do see some performance enhancements in Classic but still observe a progressively sluggish system after editing 10-30 images).

I assume that what we are seeing is not the 'norm' but I do wonder what is going on because this type of sluggishness is not typical in other products that I also use.

As many of us are long term users of Lightroom (and Photoshop) and have updated many many times over the years (both the products themselves and I would suspect the underlying operating system) - is it at all possible that old files (.dlls, etc.) are contributing to the issues?

I have not completely wiped my system clean and installed a fresh copy of Lightroom - has anyone tried this?  Even in a virtual machine?

I ask because I can not even begin to imagine that this is the 'norm' when the product team is testing the next version of the product... and I would assume that the product team likely starts with a clean system when testing?

Also, I would be interested in knowing if Camera RAW == Lightroom Develop Module... are individuals commenting on issues in Photoshop as well as it pertains to the Camera Raw module?
Inspiring
October 31, 2017
Open Begging to Simon Chen and Jeff Tranberry

Will Anyone at Adobe Ever break the Cone of Silence? Many of us have been begging for help and begging to help find and address the serious performance issues we are experiencing. 

Simon, you keep telling us "the team are working on it" and I believe you. I am just not sure what "it" is that they are working on. Clearly it has not been the performance issue. I am waiting more than one year and perhaps everyone on the "team" were too busy inventing the new cloud based product to spend any effort on the existing performance issues. Seems to me that has been quite unfair considering I pay every month for software with a major issue you have essentially ignored for more than 12 months.

Jeff, you have remained totally silent on the issue. Please tell us to go away, tell us how to fix it, tell us when we can expect some help, but please tell us something!

Both of you saw the issue while connected to my PC over one year ago and still no help and no discussion. At the PC Expo in NYC last week, I spoke to someone from Adobe that seemed quite happy when I said that I was being forced to go to Capture One and he said good if that solves my issue. Well, besides that not being a great answer, I may need to do just that. Perhaps, if those of us with this major issue went away, Adobe would be much closer to cancelling the desktop version in lieu of the new cloud based scenario that none of us could use anyway due to the lack of features and sheer volume of photos we process daily or weekly.

Many of us with strong IT backgrounds have offered to help run test products to determine the source of the issue with no response from Adobe. We have posted information trying to show how LR runs so poorly on our systems while other products seem to race along without any slowdown at all. Some of us have been forced to go back to the prior 2015.12 version so we can get our work done albeit with a restart of LR after every 30 or so images.

I am quite sure none of us want to leave Adobe and none of us want to use other products but we need your help. So, here I am begging openly for some kind of help in solving this issue. 

Most of us with the problem are using high-end PC's. I have Windows 10 on a PC with a 3.3Ghz 12-core processor, 64Mb 2400 speed RAM, NVidia GTX Titan Graphics with 12Gb Dedicated VRam, SSD drives and I can tell you that everything on my PC is lightning fast (Including Capture One and ON1 RAW 2018) except for Lightroom. 

Some of us (including me) teach comprehensive classes in both Lightroom and Photoshop and get from 30-100 students per year to enroll in the Lightroom CC (now Classic) system. Please help me continue supporting Adobe and referring students to the cloud based systems.

I am aware that my CC monthly payment means nothing to Adobe and if I went away the company would never miss it. I am aware that I am a thorn in your side for constantly complaining about performance. I am aware that the company line is that Lightroom Classic is much faster than previous versions. Well, I have yet to talk to any of my colleagues, friends, students, or anyone for that matter that thinks the new program is faster. In fact, even several of my students using MAC OS feel that Classic is slower than the prior version. Okay, I am sure some see an improvement in performance but I am not sure who they are. No matter, every day I read forum comments from many of you longest loyal customers begging for help to solve the performance issue.

So, Adobe, Jeff, Simon: I and others stand before you begging for some relief. Our businesses are suffering as we cannot process our work. Our lives are being adversely affected as we have no time left after spending three or four times as long as before working on our daily shoot images. 

Please do not force us to move away from Adobe. Many of us have been loyal supporters for dozens of years. Your company was built on our continued loyalty, software purchases, and upgrades. We really want to stay loyal. We really want to continue to recommend Adobe products to our colleagues, friends, and students. We want Adobe to continue to be the leading force in the imaging business. To do all of this, WE NEED YOUR HELP!!!

Please, please, please help us. Let us help you. We will do anything you ask of us (within reason and our busy schedules) to identify and correct this issue. I am sure you have read some of my comments on other forum threads and the times I report are real!

Many of us await your reply!!!!    PLEASE HELP US!    PLEASE TALK TO US