• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
24

P: Slow performance on Xeon CPUs

Contributor ,
Sep 22, 2016 Sep 22, 2016

Copy link to clipboard

Copied

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?

Bug Started
TOPICS
macOS , Windows

Views

4.6K

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 6 Correct answers

Adobe Employee , Nov 26, 2021 Nov 26, 2021

Set status

Status Started

Votes

Translate

Translate
Adobe Employee , Dec 13, 2017 Dec 13, 2017
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.

Votes

Translate

Translate
Adobe Employee , Nov 08, 2016 Nov 08, 2016
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.

Votes

Translate

Translate
Adobe Employee , Sep 26, 2016 Sep 26, 2016
@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 inc
...

Votes

Translate

Translate
Adobe Employee , Sep 26, 2016 Sep 26, 2016
@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...

Votes

Translate

Translate
Adobe Employee , Sep 26, 2016 Sep 26, 2016
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 an...

Votes

Translate

Translate
replies 234 Replies 234
234 Comments
Community Beginner ,
Sep 22, 2016 Sep 22, 2016

Copy link to clipboard

Copied

Which Version of Lightroom is running on that Computers?

Votes

Translate

Translate

Report

Report
Contributor ,
Sep 22, 2016 Sep 22, 2016

Copy link to clipboard

Copied

Now version 2015.7, but I tested also with 2015.5, 2015.5.1, 2015.6, 2015.6.1. The problem ist version  independent.

Votes

Translate

Translate

Report

Report
Contributor ,
Sep 22, 2016 Sep 22, 2016

Copy link to clipboard

Copied

Anyone can confirm, that LR have performance problems with clone or brush tool on workstations with 6 or more cores?

Votes

Translate

Translate

Report

Report
LEGEND ,
Sep 22, 2016 Sep 22, 2016

Copy link to clipboard

Copied

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

Votes

Translate

Translate

Report

Report
LEGEND ,
Sep 22, 2016 Sep 22, 2016

Copy link to clipboard

Copied

Note that the seemingly superfluous use of "cmd.exe" appears to be necessary due to the way that LR starts itself.

Votes

Translate

Translate

Report

Report
LEGEND ,
Sep 22, 2016 Sep 22, 2016

Copy link to clipboard

Copied

John, are you saying using Windows Task Manger's 'Set Affinity' does not work with LR?

Votes

Translate

Translate

Report

Report
LEGEND ,
Sep 22, 2016 Sep 22, 2016

Copy link to clipboard

Copied

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.

Votes

Translate

Translate

Report

Report
Contributor ,
Sep 22, 2016 Sep 22, 2016

Copy link to clipboard

Copied

a) no memory usage not increase dramatically. Memory usage stay around 30 - 50 %. Never more.

b) with your tip I tried different number of cores. With 1 core: slower, with 2 cores slower, with 3 and with 4 cores faster. The problem is not resolved with 4 cores, but seams not so dramatically. The brush is smoother and a little faster than with all 6 cores. On images with not so much local corrections, the difference (4 cores to 6 cores) is bigger (4 cores faster than 6 cores). With images with many corrections, the difference is not so big.

Seams that core support is the crucial point in LR.

Votes

Translate

Translate

Report

Report
LEGEND ,
Sep 22, 2016 Sep 22, 2016

Copy link to clipboard

Copied

I believe you indicated that with 6 cores, LR would slow down more and more after 3 photos, soon becoming unusable.  With 2 or 3 cores, LR clearly will run slower; but does it get slower over time and then become unusable, or does it just stay slow without getting worse?

Votes

Translate

Translate

Report

Report
Contributor ,
Sep 23, 2016 Sep 23, 2016

Copy link to clipboard

Copied

Unfortunaly my englisch is very bad.

a)
I would say: with 4 cores LR is faster than with 6 cores:

4 cores: faster and smoother
6 cores: slower and not so smooth

b)
Yes, LR does get slower over time and then become unusable:
with 4 cores: over more time
with 6 cores: over less time

No, when I do nothing, then no problem.

Votes

Translate

Translate

Report

Report
LEGEND ,
Sep 23, 2016 Sep 23, 2016

Copy link to clipboard

Copied

Your English is quite sufficient!

Large numbers of people use LR with 4 cores (8 virtual processors).  There have been a few reports on this forum of people successfully using 6, 8, and 10 cores (12, 16, and 20 virtual processors).   So there must be something particular about your configuration or hardware.

Votes

Translate

Translate

Report

Report
Contributor ,
Sep 23, 2016 Sep 23, 2016

Copy link to clipboard

Copied

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.

Votes

Translate

Translate

Report

Report
Contributor ,
Sep 23, 2016 Sep 23, 2016

Copy link to clipboard

Copied

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.

Votes

Translate

Translate

Report

Report
LEGEND ,
Sep 23, 2016 Sep 23, 2016

Copy link to clipboard

Copied

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/

Votes

Translate

Translate

Report

Report
LEGEND ,
Sep 23, 2016 Sep 23, 2016

Copy link to clipboard

Copied

I ran a similar LR CC2015.7 test with Canon 5Ds 50 Megapixel raw files. The Basic controls and Adjustment Brush performance was very acceptable and virtually the same as when processing Cannon 5D MKII 21 Megapixel files. Given the 5Ds resolution is more than 2x the 5D MKII files I expected to see a proportional slow down (lag) in the controls and Adjustment Brush.

What I did notice is that CPU Usage never exceeds ~50% when using the Tone controls or Adjustment. When adjusting the Detail panel Luminance slider all 8 cores (4 core processor with Hyperthreading enabled) are at 100%. This is with an i7-860 quad-core processor:

Votes

Translate

Translate

Report

Report
LEGEND ,
Sep 23, 2016 Sep 23, 2016

Copy link to clipboard

Copied

It isn't surprising that some sliders use parallelism more effectively than others.  Adobe engineers have long indicated that much of the Camera Raw pipeline is inherently not easily parallelizable (thus, the difficulties of effectively using GPUs).  

Votes

Translate

Translate

Report

Report
LEGEND ,
Sep 23, 2016 Sep 23, 2016

Copy link to clipboard

Copied

"I think that this excludes memory problems."

Agreed.

Votes

Translate

Translate

Report

Report
LEGEND ,
Sep 23, 2016 Sep 23, 2016

Copy link to clipboard

Copied

"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"

Thanks for finding that. I searched last night for similar reports but didn't find any.  I'll consider whether to merge this topic in with the others.   In general, it's important that all the reports of similar problems are merged into one thread, so that Adobe can properly appreciate the scope of the problem. But merging partially hides the existing replies.

Votes

Translate

Translate

Report

Report
Contributor ,
Sep 24, 2016 Sep 24, 2016

Copy link to clipboard

Copied

I had already tested with hyperthreading off. Slight improvement, but only very slightly...

Votes

Translate

Translate

Report

Report
Contributor ,
Sep 24, 2016 Sep 24, 2016

Copy link to clipboard

Copied

What I did notice is that CPU Usage never exceeds ~50% when using the Tone controls or Adjustment.
I can confirm. Hyperthreading on/off no big difference.

Votes

Translate

Translate

Report

Report
LEGEND ,
Sep 24, 2016 Sep 24, 2016

Copy link to clipboard

Copied

I have just a horrific experience with performance and lightroom in Windows 10 with a Xeon CPU Desktop I built for Photo Editing in Lightroom/Photoshop and video editing. 

Premier, Photoshop, work tremendously well - no issues. 

Lightroom - a piece of garbage. 

https://forums.adobe.com/message/9026722#9026722

Votes

Translate

Translate

Report

Report
Advocate ,
Sep 25, 2016 Sep 25, 2016

Copy link to clipboard

Copied

I have an i7-5830K cpu and rendering 1:1 previews takes about 6/7 secs with 6/12 processors, but 10/12 secs using just 4/8 processors. So LR does seem to be able to use 6/12 processors efficiently.


Bob Frost

Votes

Translate

Translate

Report

Report
LEGEND ,
Sep 25, 2016 Sep 25, 2016

Copy link to clipboard

Copied

How does your system perform with  extensive Adjustments Brush or Clone tool usage, Crop tool, Tone control slider response, Luminance slider response, or other performance issues after editing multiple image files. That's what the OP here is complaining about. More details: https://forums.adobe.com/thread/2210245

Votes

Translate

Translate

Report

Report
Advocate ,
Sep 25, 2016 Sep 25, 2016

Copy link to clipboard

Copied

I don't have any other slow problems, only preview rendering slowing down with time - overnight for example. I don't have a 4K monitor, but I can use the performance setting for gpu without problems. My graphics card is a Quadro K2000; NVidia and AMD cards often gave problems in the past since the drivers are designed for games. The Quadro drivers are designed for stability.


Bob frost

Votes

Translate

Translate

Report

Report
LEGEND ,
Sep 25, 2016 Sep 25, 2016

Copy link to clipboard

Copied

The OP here is using a Quadro K5000 with the latest drivers, so his issue is related to the 6-core Xeon processor. I'm using an i7-860 quad-core processor and low-end Quadro 600 graphics card. With GPU enabled the only issue I have is that it slows down the Adjustment Brush and Luminance slider so I generally keep it disabled. My modest system with 21 Megapixel raw files and a 2560 x 1440 monitor runs quite well, even when making extensive local adjustments to a large number of files. It's a mystery why some 6-core and higher systems have these performance issues.

Votes

Translate

Translate

Report

Report