Lightroom: Slow performance on Xeon CPUs

  • 22
  • Problem
  • Updated 6 months 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 2 years ago

  • 22
Photo of Stefan Redel

Stefan Redel

  • 88 Posts
  • 29 Reply Likes
Which Version of Lightroom is running on that Computers?
Photo of Dietmar Mitterer Zublasing

Dietmar Mitterer Zublasing

  • 29 Posts
  • 11 Reply Likes
Now version 2015.7, but I tested also with 2015.5, 2015.5.1, 2015.6, 2015.6.1. The problem ist version  independent.
Photo of Hagens World Photography

Hagens World Photography

  • 5 Posts
  • 0 Reply Likes
I can confirm the problem with a E5-1650 v4
Photo of Igor Socha

Igor Socha

  • 7 Posts
  • 6 Reply Likes
I have exactly the same problem with E5-1620 v3 @3.50GHz and last LR (at the moment CC 2015.8)
Photo of Dietmar Mitterer Zublasing

Dietmar Mitterer Zublasing

  • 29 Posts
  • 11 Reply Likes
Anyone can confirm, that LR have performance problems with clone or brush tool on workstations with 6 or more cores?
Photo of John R. Ellis

John R. Ellis, Champion

  • 3589 Posts
  • 928 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

  • 170 Posts
  • 40 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

  • 3589 Posts
  • 928 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 Todd Shaner

Todd Shaner, Champion

  • 993 Posts
  • 324 Reply Likes
John, are you saying using Windows Task Manger's 'Set Affinity' does not work with LR?

Photo of John R. Ellis

John R. Ellis, Champion

  • 3589 Posts
  • 928 Reply Likes
No. The use of "cmd.exe" is required with the "start" command, probably because of something funky LR does on its start up.

I don't think using the Task Manager to set affinity of a running LR process would be as good a test. It's possible that LR makes some decisions about how many processors to use early in its startup sequence, and setting affinity with the Task Manager would be too late.
Photo of Todd Shaner

Todd Shaner, Champion

  • 993 Posts
  • 324 Reply Likes
That makes sense. On startup LR determines the available processor cores and distributes the workload using a muli-processing algorithm. With 6 or more cores the algorithm fails and LR's performance drops. If this is the case then restricting the available cores on systems with 6 or more core processors should improve performance. I suggest also testing with hyperthreading both enabled and disabled in the system BIOS.

Puget Systems did similar testing of LR6, but they didn't run any benchmarks for Develop module control performance (Tone, Adjustment Brush, etc.).
https://www.pugetsystems.com/labs/articles/Adobe-Lightroom-CC-6-Multi-Core-Performance-649/
Photo of Dietmar Mitterer Zublasing

Dietmar Mitterer Zublasing

  • 29 Posts
  • 11 Reply Likes
I had already tested with hyperthreading off. Slight improvement, but only very slightly...
Photo of Mihael Tominšek

Mihael Tominšek

  • 37 Posts
  • 31 Reply Likes
Affinity has no point whatsoever. On my 6/12-core at least not. This is complete nonsense. 
Lightroom uses all cores (all 12 logic cores) when exporting, creating 1:1 previews etc. While editing it uses for 1 core of power, maybe 2. I can set affinity to only 1 core and performance would not suffer mauch. But it would be huge difference on export. If U se GPU there is boost in performance regardless of number of cores. But for brush, I need to switch off GPU in settings. Which is annoying, and I do not do it always. Brushes doing ok under GPU, I just do not see what I'm, painting until I stop and area get overlay. For simple things I paint on "air". If I need to be precise, I turn GPU off. Annoying. SInce I use Lr only for "preset/auto" stff latelly I don't care anymoore. Adobe will lost one customer when my 1 year CC runs off. No point wasting my creative life here. 100's of replyes and no solution. It can't be...
Photo of Dietmar Mitterer Zublasing

Dietmar Mitterer Zublasing

  • 29 Posts
  • 11 Reply Likes
Also interesting: I have made all tested with photos of my D5100 (RAW 15 MB). Now, I tested with photos of my D800E (RAW 35 MB). The problem remain exact the same. It is interesting, that the problem is not aggravated with bigger images. Exact the same.

I think that this excludes memory problems.
Photo of Todd Shaner

Todd Shaner, Champion

  • 928 Posts
  • 281 Reply Likes
Agreed. We've seen reports with this type of performance issue from users with Intel i7 and Xeon processors as well as AMD processors. The one common element is that their processors are six or more cores.
Photo of Igor Socha

Igor Socha

  • 7 Posts
  • 6 Reply Likes
My CPU is 4 core Xeon 1620 v3 and I have the same problem. While working, LR is gradually becoming slowlier but the task manager says only about 25 - 35% of my system resources are used (I have 32GB RAM). Weird :(
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1387 Posts
  • 414 Reply Likes
When Lr starts to getting slower, in addition to the RAM usage, can you check in the Windows Task Manager and note what the reported Lightroom usage for the GDI Objects, Threads, Handles and User Objects?
Photo of Oleksandr Petrenko

Oleksandr Petrenko

  • 17 Posts
  • 0 Reply Likes
I observe the same (slowdown of LRwith more editing) problem on i7/4 core MacBook. All adjustments are basic (no healing brushes or selective adjustments).
Photo of Oleksandr Petrenko

Oleksandr Petrenko

  • 17 Posts
  • 0 Reply Likes
I observe the same (slowdown of LRwith more editing) problem on i7/4 core MacBook. All adjustments are basic (no healing brushes or selective adjustments).
Photo of Assaf Frank

Assaf Frank

  • 147 Posts
  • 46 Reply Likes
you will also notice that if you export images after lightroom restart it will be much faster and the CPU will reach 100% but if you do the same export after working on some images and the slowness sets in the same export will take much longer the lightroom will not max out the CPU usage. see more on this tread. https://feedback.photoshop.com/photoshop_family/topics/lightroom-image-export-is-much-faster-after-restart-cc-2016-6-1-and-before I suspect this is also linked to 6 or more CPUs as you will see on the link above when Stefan tried to replicate it on 4 cores CPU there was no reduction in speed.
Photo of Dietmar Mitterer Zublasing

Dietmar Mitterer Zublasing

  • 29 Posts
  • 11 Reply Likes
This is definitely my last test (I spend a lot of time for testing)!

In forum adobe a user sad: downgrade to 2015.4 helps.

I tested it. Result: not helps!

Photo of Robert Frost

Robert Frost

  • 392 Posts
  • 51 Reply Likes

Can we have a comment from Adobe on this please. Can't you replicate it?


Bob frost

Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1417 Posts
  • 437 Reply Likes
Official Response
What does Lightroom's Help>System Info... say? It should report the processor count and the maximum number of thread count used by the image processing pipeline?

Some made the observation that Lr was performant right after a launch and then gets slower after intense brushing. Is it on a single photo or do you typically have to walk several photos to reproduce it? Do you remember which version of Lr this started to happen? Do you have Lr mobile sync turned on? What happens if you pause the sync and then relaunch Lr?
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1417 Posts
  • 437 Reply Likes
Official Response
@Dietmar reported that the issue is found to be in 2015.5, 2015.5.1, 2015.6, 2015.6.1 as well. It would be helpful to post the Lightroom's Help>System Info...
Photo of J Ray Sanduski

J Ray Sanduski

  • 3 Posts
  • 0 Reply Likes
I started having slow performance issues around August of this year - 2016 - It was after an update was installed, but I do not recall what the version number was!
Photo of John R. Ellis

John R. Ellis, Champion

  • 3586 Posts
  • 926 Reply Likes
LR CC 2015.6.1 was released 7/25.   So you might consider rolling back to 2015.6: https://helpx.adobe.com/lightroom/kb/roll-back-to-prior-update.html
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1417 Posts
  • 437 Reply Likes
Official Response
@Dietmar You've provided additional detailed info in https://forums.adobe.com/thread/2210245. That is very helpful. Are the summary of your previous findings (copied as-is) still applies with the Lr 2015.7 and Camera Raw 9.7 release?

Summary
  1. LR/Camera Raw has definitive a performance problem with some - especially my high-quality – PCs!
  2. I can reproduce the problem and I can demonstrate that the problem on other - especially my weak – PCs not persist or is not so strongly.
  3. With GPU on the problem increase drastically!
  4. Camera RAW from Bridge and Photoshop have the same problem.
  5. With higher lightroom version the problem increase! Also with the newest 2015.6.1!
  6. Camera Raw Cache amll/big. No difference.
  7. Minimize LR, not helps or helps only minimal.
  8. Downgrade helps a little, but not eliminate the problem in general.
  9. Restart LR, helps but restart LR every X images are not a good workaround!
  10. It is very frustrating that with LR my weakness machine is better than my best PC!
Photo of Dietmar Mitterer Zublasing

Dietmar Mitterer Zublasing

  • 29 Posts
  • 11 Reply Likes
Attention: your tests are renderung, my tests are edits. It is not the same.

Yes you are right. Has do do with edits!

But why the PC goes slower and slower also when I step to another photo? And why the PC not return fast when the CPU utilization goes to zero? And why I can not reproduce the problem on my weak PC?

I think the problem is more complex: has do do with edits, CPU number, resolution etc. In my opinion, a fundamental problem in the kernel programming...

I hope in a revision of kernel programming of LR...
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1417 Posts
  • 437 Reply Likes
Our engineers are looking into this. Is your known method to "reclaim" some speed back is to restart Lightroom/ACR? 

@Dietmar For your Lightroom slow down issue, could you try the following

  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 http://adobe.ly/2cEF782 and download the config.lua file and copy it into the root preset folder (under "Lightroom") at step 5. The config.lua file will reconfigure some Lightroom RAM usages for caching. 
  7. Relaunch Lr and follow your normal routines to reproduce the issue to see if it improves. You can also try to tweak the numbers to see if it makes any difference.
  8. Remove or rename the config.lua from the root preset folder after the experiment (to restore to the original Lr 6.7 behavior). 
Photo of Robert Frost

Robert Frost

  • 392 Posts
  • 51 Reply Likes

For my rendering slow-down, the only way to reclaim speed is to restart LR. Simply stopping rendering and letting LR settle down and then restarting rendering does not speed things up. I'll let Dietmar deal with the editing slow-down.


Bob F

(Edited)
Photo of Dietmar Mitterer Zublasing

Dietmar Mitterer Zublasing

  • 29 Posts
  • 11 Reply Likes
@Simon Chen

a)
Yes, I can "reclaim" the speed with restart of Lightroom

b)
Now I tested your suggestion with the config.lua file.
Result: unfortunately no solution :-(
Photo of Todd Shaner

Todd Shaner, Champion

  • 989 Posts
  • 324 Reply Likes
Simon, what exactly does the config.lua file do? You also mention tweaking the numbers, but what do they mean and how should you change the values?

AgGCCache.mainCacheFactor = 0.1
AgNegativeCache.factorOfAddressSpace = 0.01
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

  • 147 Posts
  • 44 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

  • 392 Posts
  • 51 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 Arnold Bartel

Arnold Bartel

  • 170 Posts
  • 40 Reply Likes
Servus Dietmar,
I'm using LR on an i7 6 core machine and after upgrading to a 4k display I'm experiencing similar massive performance problems.
Photo of John Ott

John Ott

  • 8 Posts
  • 2 Reply Likes
Same here and I've recently upgraded to a 10 core machine with a 4K display. It is so slow processing after the first few images that I just gave up. I'm using C1 in the interim until there is some sort of fix out.
Photo of J Ray Sanduski

J Ray Sanduski

  • 3 Posts
  • 0 Reply Likes
I have a 4k display with an 8 core i-7 with 24GB RAM and I am basically dead in the water - I have been editing the same wedding since last Wednesday (5 days so far - 1800 .nef's!)

I can not live like this!  I will have to go back to using the Photoshop Image processor if this does not change soon!
Photo of Robert Frost

Robert Frost

  • 392 Posts
  • 51 Reply Likes

Here is an interesting article on Lightrooms performance with differing core number -

https://www.pugetsystems.com/labs/articles/Adobe-Lightroom-CC-6-Multi-Core-Performance-649/

Bob frost

Photo of Todd Shaner

Todd Shaner, Champion

  • 911 Posts
  • 279 Reply Likes
The problem with that article is that no "editing" benchmarks were tested, such as using the Adjustment Brush and Clone tool, etc. I'm sure if they did the issues reported here would have surfaced. The benchmarks do clearly indicate there's little to be gained going beyond 4-cores.
Photo of Rob van den Wijngaart

Rob van den Wijngaart

  • 12 Posts
  • 3 Reply Likes
Photo of Todd Shaner

Todd Shaner, Champion

  • 894 Posts
  • 275 Reply Likes
The above link references performance issues with a Xeon 6-core system that only started after updating from LR 6.6.1 to 6.7. Rolling back to 6.6.1 resolved the issues for this user.
Photo of Stefan Dawid

Stefan Dawid

  • 4 Posts
  • 2 Reply Likes
i7 -3770k w Win10 here with 16 GB RAM, Sapphire 7850 @ 1920x1200; latest Lightroom 6.7 on fast SSD with plenty of free space. Same issues: over about 20 spot adjustments and brushes on a single photography LR starts lagging terribly.

Using a brush it takes up to 20/30 seconds just for the red overlay to display over the area I just brushed. Same for additional spot tool edits. LR basically becomes unusable.
Hw acceleration on or off does not make any significant difference.

Frankly speaking it is unacceptable for a professional photography software as LR is supposed to be.

Even more it seems there is no developer feedback on this matter.
Not exactly the type of support you'd expect.
Photo of Patrice Mestari

Patrice Mestari

  • 7 Posts
  • 2 Reply Likes
Same problem Dawid.. I have Macbook Pro I5 2.9Ghz SSD 512, Ram 8go.. 
Photo of Reed Radcliffe

Reed Radcliffe

  • 6 Posts
  • 3 Reply Likes
I upgraded my machine from an I7 4790 and 16gb of ram with a 1tb SSD drive to one with an I7 6700HQ 64gb RAM and two 1tb SSD drives - keeping the cache on a separate drive. I did this because I thought I had worn out the old machine because LR CC had started to run so slowly. It runs just as slowly on the new machine and it is becoming extremely frustrating.

When will Adobe address this issue?
Photo of Todd Shaner

Todd Shaner, Champion

  • 618 Posts
  • 176 Reply Likes
According to PassMark's benchmarks the i7-6700HQ (8,023) is a lower performance processor than your previous i7-4790 (9,995). Also moving caches to a separate SSD has very little affect on LR's performance. What exact version of LR are you using, what OS version, what is your monitor's resolution, and are you using dual-displays?
Photo of Reed Radcliffe

Reed Radcliffe

  • 6 Posts
  • 3 Reply Likes
Actually the mobile 4790 - I read it is somewhat of a wash.

I'm on a 17" laptop, no dual displays, WIN 10 Anniversary edition and the latest update to LR 6. It's been creeping since the spring starting on the old machine which had been upgraded over and over. I thought the brand new build and hardware would change things.

One thing did help a little after reading this thread yesterday was turning off the GPU on my Invidia 1070 video card for Lightroom. I used the Invidia settings. It still lags a little when going from one photo to the next or pasting settings or adjustment brushing any amount at all, but not the four or five seconds it was taking.

In all, we shouldn't even be having this conversation. LR has an issue that we should not have to tweak away.
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1417 Posts
  • 437 Reply Likes
Official Response
Can you folks pin-point for certainty the specific version of Lightroom that starts exhibiting the same performance issue under the same machine setup? That would be helpful us to figure what happened. 

Here is a link where you can rollback to the earlier Lightroom versions https://helpx.adobe.com/lightroom/kb/lightroom-downloads.html.
Photo of Rob van den Wijngaart

Rob van den Wijngaart

  • 12 Posts
  • 3 Reply Likes
After the update to 6.7 the processor use goes to 100% when opening lr. Went back to 6.6.1 now it okay. Other problem with brushes and things like that I have too, thought that it a problem with my pc, but according to others its aldo an lr problem. My computer a Dell T5600 xeon 6 core with 24Gb memory.
Photo of Scott Wild

Scott Wild

  • 20 Posts
  • 28 Reply Likes
Similar problems here too.
My 2013 Macbook Pro pushing the same 3440x1440 display is twice as fast as my new build (Windows 10 x64, i7-6900K, GTX1080, Samsung 950 Pro and 850's, 64GB Ram).

Why is this???

For importing 1,500 images and building 1:1 previews it's twice as fast...I've timed it.
The develop module loads faster and is far more responsive as well.

Can someone please help?
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 Assaf Frank

Assaf Frank

  • 147 Posts
  • 46 Reply Likes
Great news, its a shame that no one in Adobe even tought to do the simple thing and let us know its a known issue and they are working on it. Anyway don't build your hopes up for a complete fix in the next version. Probebly we are going to get another automatic f#@!*** recognition tool that streach your face on selfies before they fix it. This issue with performance on high end hardware was since the beginning. They did sort some issues with memory leaks but for the most of us it is faster after restart then when you work on few images it is slow again. So restarting seems to fix it. But we cant restart all day. Also image export is much faster after restart.
(Edited)
Photo of John Ott

John Ott

  • 8 Posts
  • 2 Reply Likes
Well I hope the fix comes sooner rather than later and will agree that having to restart Lr after processing a few photos is killing me.  I have been using C1 just to get by and that software seems to take good advantage of the hardware I already have and is lightning fast with my setup.  

Once the fix is out, I would be curious as to what the underlying issue was. I am really hoping that Adobe wasn't blowing smoke Scott and they are working on 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 John Ott

John Ott

  • 8 Posts
  • 2 Reply Likes
Glad to hear it Scott!  Now to wait patiently I guess...