Lightroom: Slow performance on Xeon CPUs

  • 23
  • Problem
  • Updated 2 years ago
  • (Edited)
I noticed that LR clone and brush tool on my XEON E5-1650 0 3.20GHz (Attention: E5-1650 0 and not E5-1650 v4) can not stress my CPU and after x minutes of working LR slow down, until I have to restart it.

Please see the full diskussion with the problem here: https://forums.adobe.com/thread/2210245 (test with different Lightroom versions, confrontation with a weak laptop, that works fine, tests wit other graphic grafic card, test with other bios settings etc. No results. Only restart LR or minor display resolution helps.)

Can anyone with an XEON E5-1650 0 3.2Ghz confirm this?
Photo of Dietmar Mitterer Zublasing

Dietmar Mitterer Zublasing

  • 29 Posts
  • 11 Reply Likes
  • frustrated

Posted 3 years ago

  • 23
Photo of John R. Ellis

John R. Ellis, Champion

  • 4455 Posts
  • 1182 Reply Likes
Reading through the extensive discussion in the other thread, two other troubleshooting steps come to mind:

- Does LR's memory usage as reported in Task Manager increase dramatically as it slows down?   That's a typical symptom of a memory leak.

- Try restricting LR to running on 1, 2, 3, or 4 processors.  Open a command prompt and paste this line:
start /affinity F cmd.exe /c "c:\Program Files\Adobe\Adobe Lightroom\lightroom.exe"
An affinity mask of "F" specifies 4 processors; use "7" for 3 processors, "3" for 2 processors, and "1" for 1 processor. (The mask is a bit mask specified in hex.) 
Photo of Dietmar Mitterer Zublasing

Dietmar Mitterer Zublasing

  • 29 Posts
  • 11 Reply Likes
But I find here in the forum also people using 6 and more cores with problems! Examples: https://feedback.photoshop.com/photoshop_family/topics/lightroom-2015-6-extremely-slow

But yes, I think it's a combination of LR-PC-Configuration.

I exclude the graphics card, because I have already tested with two different cards in the same PC. And I exclude drivers, because I have updated all system components.

Now I look for people who also have a XEON E5-1650 0 3.2Ghz and be able to report their experiences.
(Edited)
Photo of Arnold Bartel

Arnold Bartel

  • 196 Posts
  • 53 Reply Likes
I did some tests and can confirm this behaviour:
using a 6 (12) core i7 machine with a 4k display makes Lightroom nearly compleately non-usable!
reducing the used cores by the described command above and reducing the display resolution speeds LR up.
In my eyes it is absolutely inacceptable that the leading application for photography pros shows this behaviour. It's exactly this group of users who will use 4k displays and high performance PCs on which LR fails and slows down rapidly!
Photo of Tommie Hansen

Tommie Hansen

  • 1 Post
  • 1 Reply Like
I specifically use a 4k screen for editing but also for coding since all the text is easier on the eyes for longer durations of times.

But seriously -- even if not photography 4k isn't really exotic anymore. It's mostly gamers that still buy 1080p screens.

What i would like to see is that the Develop Module in Lightroom is 100% dedicated to the task at hand. Editing photos shouldn't be anywhere near slow on a modern system.
(Edited)
Photo of Orjan Ellingvag

Orjan Ellingvag

  • 7 Posts
  • 2 Reply Likes
Thank you John R. Ellis!  Did try the John R. Ellis solution, and so far LR CC runs smoothly for the first time in ages. If only I had known 3 years ago. I have had the lagging/sluggish issue for years, with different versions of LR (both CC and standalones), and always suggested memory leak as the culprit.  For now, I made a .bat-file with John's line, and will test it thoroughly. So far Adobe have only suggested various work-arounds (smaller catalogs, no batch editing etc.), but reducing the core affiliation actually taste like a real solution (and pin-pointing a serious software issue)

w10x64 w/i7 3770K cpu @3.5ghz. OS, storage and scratch disks are on 3 separate 0-raided ssd's. The gpu is an amd r9 380. Asus Maximus V mobo
Photo of John R. Ellis

John R. Ellis, Champion

  • 4455 Posts
  • 1182 Reply Likes
What value did you use for the affinity mask?

Limiting the number of processors is an old debugging trick to help identify race conditions in multi-threaded programs. There's pretty clearly some problem with how LR uses multiple processors on some CPUs.
Photo of Dietmar Mitterer Zublasing

Dietmar Mitterer Zublasing

  • 29 Posts
  • 11 Reply Likes
I think I forgot an important point on my summary (in the adobe forum I have said it):
Point 11: When I reduce the resolution of my the display to 1280x1024 that helps a lot. Then slow down only  after more time... 

I would say that the problem "slow down" has to do with not only with cpu, but also with display resolution ( but not with graphic cards or driver because I tested with different graphic cards).

P.S. Is here anyone from Adobe? I wonder if it makes sense post experiences, or it is lost time? A statement: We know the problem and working on it, would help;-) 
Photo of Assaf Frank

Assaf Frank

  • 148 Posts
  • 46 Reply Likes
everything you have just said has been reported before:
slowness on hi resolution displays.
slowdown after working on some images and need to restart

the new thing is that you managed to narrow the decreasing performance problem to more than 4 CPU's which is a progress.

also there is a significant reduction in the speed of image export if lightroom was open and some image editing was done prior to the export. if you want fast export then restart lightroom then do the export or press the publish button.

Adobe at least tell us if you can replicate the problem or not and stop wasting our time on this forum.

don't keep us in the dark!

I live near the Adobe HQ in Maidenhead Berkshire, UK. I can bring my computer to you and show you all those issues. we can install testing software on it. anything you need. my copmuter is i7 5960X 8 core + 4K display which has similar issues to the xeon CPUs

let me know.
(Edited)
Photo of Robert Frost

Robert Frost

  • 426 Posts
  • 72 Reply Likes

There seems to have been no change in this problem since my last thread on this subject in June 2015.

Bob Frost

Photo of Scott Wild

Scott Wild

  • 20 Posts
  • 28 Reply Likes
OK, spoke with Adobe support this afternoon and they acknowledge a problem with multi core processors (more than 4) and high end graphics cards with Lightroom. They said they have engineers working on the problem and unfortunately don't have a timeline for a fix. 
Photo of Scott Wild

Scott Wild

  • 20 Posts
  • 28 Reply Likes
I spoke with basic tech support and grilled the guy with questions...he didn't seem to be aware of the issue. He escalated the call to the tech support manager. The manager immediately fluent with the problems I was having. He told me the Adobe engineers are aware of the multi-core problem as well as the high end graphics card issues and are working towards a solution.  If he was lying he was a damn good liar.
Photo of David Kkozi Lejček

David Kkozi Lejček

  • 5 Posts
  • 4 Reply Likes
After a couple of months having problem with Lightroom I got to this site. I tried everything, read milions comments and topics on forums and I solved nothing with the performance issues.
I edit hundreds or thousands of pictures from every shooting and lightroom became to be pain in the ass processing the photos.

I tried different sw to process raw. Capture one 10 is really really fast, has the quality but the noise and image quality what lightroom has is the best for my eyes.

I hope that Adobe will update LIghtroom with all the performance issues fixed soon. It is a huge Adobe fail. Huge one!
Photo of Dietmar Mitterer Zublasing

Dietmar Mitterer Zublasing

  • 29 Posts
  • 11 Reply Likes
Yes, the whole thing is extremely frustrating.

My workarounds are:
A) Re-start Lightroom every 5 min
B) Edit with lightroom mobile
Both, a catastrophy when you have to edit many photos :-(
Photo of Assaf Frank

Assaf Frank

  • 148 Posts
  • 46 Reply Likes
I can't believe C1 noise is worse then lightroom, I have the opposite issue, but it is depending on the camera specific raw file.
I suggest you open a support ticket with capture 1 and show them the 2 results c1 vs lightroom, they will be very quick to reply. 1-3 days normally.
Photo of David Kkozi Lejček

David Kkozi Lejček

  • 5 Posts
  • 4 Reply Likes
Really? Cool. I will try to send it them. There is a small difference but it's noticable (for pixel peeper :-)
In Capture One it looks like compression noise and in Lightroom it is more like film grain and more natural.

Thank you for the advice.
Photo of Mihael Tominšek

Mihael Tominšek

  • 37 Posts
  • 31 Reply Likes
I have experience with C1 v9. Noise reduction is mixed bag compared to Lr. It is worse on large clean areas like arhitecture, but is better on detailed things. I like Color NR in Lr, but I dislike that Lr hardly fix stubborn white dots. For ultimate NR I have external app anyway. So C1 vs Lr noise reduction is irrelavant. I mostly do not apply NR on both. I just add grain. Which is more natural in C1 for my eyes.
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1573 Posts
  • 514 Reply Likes
There has been some under-the-hood threading changes in Lr CC 2015.10 (Lr 6.10), the team like to hear your feedback on if anything has changed for you with the Lr CC 2015.10 (Lr 6.10) update.  Furthermore, we have added some configuration flag that allows tweaking how Lightroom makes uses of the multiple CPU cores. If the problem still persists, you could do a test as described below and report back if you can get improved interactive editing performance:
  1. Open Lightroom.
  2. Invoke Lightroom > Preferences... menu command
  3. When the Preferences dialog appears, select the Presets tab.
  4. Click on the button labeled “Show Lightroom Presets Folder...”
  5. Lightroom will reveal the root preset folder in the Finder/Explorer.
  6. Now goto https://adobe.ly/2oqzWOX and download the config.lua file and copy it into the Lightroom preset folder that Finder/Explorer selected at step 5. The config.lua file will set a ratio (<=1.0, default is 1.0) on the maximum number of concurrent threads that Lr would use as relative to the total number logical CPU cores on the machine.
  7. Relaunch Lr. If you did step 1 though step 6 correctly, you should see the following entry reported in Lightroom's System Info dialog, which will essentially instruct Lr to not use more than the number of physical CPU cores of threads plus 1.
Config.lua flags: 
Develop.AdjustMaximumThreadCount = 0.51

     8. Now do your normal thing in Lr and report back your experience.You can further tweak the value of "AdjustMaximumThreadCount" in the config.lua file to see if things changes for you.
     9. Remove or rename the config.lua from the Lightroom preset folder after the experiment.
(Edited)
Photo of Assaf Frank

Assaf Frank

  • 148 Posts
  • 46 Reply Likes
Hi Jerry,

can you let me know the what is the line in the config.lua
and do you notice any degradation in performance after a while
and what is your spec (CPU/GPU/OS)

Thank you in advance.
Assaf
Photo of Jerry Syder

Jerry Syder

  • 292 Posts
  • 139 Reply Likes
Oh dear!!! I may have been a bit hasty in my response ;-(!! Ashamed of myself, I stayed quiet until someone called me out. I guess when something appears too good to be true, they are in fact, too good to be true. Two things 1. I was using smart objects so this was not a fair test as I was not working on the full RAW file. 2. Things did degrade after about 10mins or so. n.b I switched off Smart Previews to see what it would be like - result, laggy but I must admit that after testing both cases(with or without smart previews) things are marginally better than before but nothing to jump and scream about. Also, in both cases, things did degrade after minutes of a LR restart.

Config.lua flags:
Develop.AdjustMaximumThreadCount = 0.51

Lightroom version: CC 2015.10 [ 1111918 ]
License: Creative Cloud
Operating system: Windows 10
Version: 10.0
Application architecture: x64
System architecture: x64
Logical processor count: 8
Processor speed: 3.4 GHz
Built-in memory: 16325.8 MB

Graphics Processor Info:
GeForce GTX 1060 6GB

..............................

Now I go bury my head 
Photo of Assaf Frank

Assaf Frank

  • 148 Posts
  • 46 Reply Likes
No worries mate, I have also started using smart previews and it makes a big difference, but it is not ideal when you need to check focus and zoom in, but it is defiantly more responsive.

The main issue I want adobe to concentrate is the performance degradation.

after restart everything is always much faster (without smart previews) and also creating panoramas are half the time if not less.
my Config.lua flags is the same: 
Develop.AdjustMaximumThreadCount = 0.51

which I think makes a some difference in performance.
but hey fix the performance degradation...

we had enough restarting lightroom every time we want to speed up things.
(Edited)
Photo of Jerry Syder

Jerry Syder

  • 292 Posts
  • 139 Reply Likes
Haha! I know the feeling buddy. If only it continued working as when we first launched the program. I think they are working on something to nail this issue finally so fingers crossed. 
Photo of Robert Frost

Robert Frost

  • 426 Posts
  • 73 Reply Likes

Hi Simon,

I tried your config.lua a while ago and found no difference in the slowdown in rendering with time, BUT have now realised I had it in the wrong LR folder!!! Copying the .51 config.lua to the correct folder seems to have cured the slowdown in rendering D810 nefs. Early days, but I have just rendered about 1200 nefs without any slowdown!

I haven't tried the config.lua with 0.5 but will do later.

Some months ago, I had a look at what LR is doing during rendering with MS Process Monitor (filtered on lightroom.exe). I could see that when rendering became slow after an hour or more, it seemed to be spending more time creating and closing threads without anything happening (the RH side of the data lines were full of zero times). Is that the logjam; too many threads being created which can't get onto the 'motorway' and thus wasting LR time? Just had a look again at it running with 0.51 after 1200 renders and there seem to be far fewer threads being created and closed than before. I'm not a programmer, but this did seem to be a clue to me.

I'll let this rendering continue for another hour or so, and then try the other setting, but you might, just might, have solved my slowdown problem. Never had a slowdown with editing, but then I don't sit editing for hours - it's my hobby, not work ;)

Bob Frost

Photo of Chris Page

Chris Page

  • 8 Posts
  • 3 Reply Likes
I am losing the will to live......adobe needs to get their finger out, my i7 can happily churn using all cores on Lightroom processing, it needs them but when I am working through adding keywords I gradually get slower and slower performance until I get a non responding lightroom. If I kill lightroom before it becomes terminal my PC continues with no issues. Basic software problems on professional, and not cheap, software really isn't acceptable in this day and age.
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1573 Posts
  • 514 Reply Likes
Official Response
If you are an existing Lr Classic CC customer, and would like to test out a developer preview build that we think fixes this performance issue. Please send me a note and I'll make sure that you are invited to the prerelease program. Thanks.
Photo of Paul Monckton

Paul Monckton

  • 3 Posts
  • 0 Reply Likes
I have the same issue as Reed Radcliffe but didn't want to post my main email address here because of spam issues.
Photo of LanceUEP

LanceUEP

  • 4 Posts
  • 3 Reply Likes
I am interested in trying the developer preview please! Thank you!
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1573 Posts
  • 514 Reply Likes
You can send me direct message with your email address, Lance, direct message to me with your email address as well.
(Edited)
Photo of Paul Monckton

Paul Monckton

  • 3 Posts
  • 0 Reply Likes
Hi Simon, I don't seem to have the right permissions to be able to send you a direct message on here.
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1573 Posts
  • 514 Reply Likes
Drop me a note: sichen AT adobe DOT com.