Skip to main content
Adobe Photoshop Family

32 Messages

 • 

870 Points

Thu, Sep 22, 2016 8:45 AM

Lightroom: Slow performance on Xeon CPUs

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?

Responses

443 Messages

 • 

6.6K Points

4 years ago

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

Champion

 • 

2.2K Messages

 • 

37.4K Points

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.

12 Messages

 • 

244 Points

4 years ago

Champion

 • 

2.2K Messages

 • 

37.4K Points

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.

4 Messages

 • 

132 Points

4 years ago

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.

7 Messages

 • 

166 Points

Same problem Dawid.. I have Macbook Pro I5 2.9Ghz SSD 512, Ram 8go.. 

6 Messages

 • 

174 Points

4 years ago

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?

Champion

 • 

2.2K Messages

 • 

37.4K Points

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?

6 Messages

 • 

174 Points

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.

12 Messages

 • 

244 Points

4 years ago

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.

20 Messages

 • 

796 Points

4 years ago

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?

20 Messages

 • 

796 Points

4 years ago

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. 

150 Messages

 • 

2.9K Points

4 years ago

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.

8 Messages

 • 

174 Points

4 years ago

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

20 Messages

 • 

796 Points

4 years ago

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.

8 Messages

 • 

174 Points

4 years ago

Glad to hear it Scott!  Now to wait patiently I guess...

5 Messages

 • 

188 Points

4 years ago

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!

32 Messages

 • 

870 Points

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 :-(

150 Messages

 • 

2.9K Points

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.

5 Messages

 • 

188 Points

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.

39 Messages

 • 

1.1K Points

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.

8 Messages

 • 

174 Points

4 years ago

Well it looks like Lr CC 2015.8 just released that has various bug fixes as well as fixed more memory leaks. I am curious to see if our issues got resolved. I will download it tonight to see if everything is working as expected

20 Messages

 • 

796 Points

Yes, please do. Keep us posted, thanks!

6 Messages

 • 

174 Points

The new update to Adobe Lightroom CC (2015.8) is a big improvement. My video card (Invidia 1070) with the latest driver is now recognized as working in LR and things are loading better, adjustment brushes are quicker (not yet snappy, but better by a fair margin) and exports are now faster.

8 Messages

 • 

174 Points

Glad to hear it! I've got an event to shoot today so I will be able to put the new update through the paces. Will report back my results

12 Messages

 • 

244 Points

Lest see what happens. Just installed the update to 6.8. Gonna work tomorrow on photos.

5 Messages

 • 

188 Points

I am working on hundreds of photos nad it's still the same. I tried to use graphic card and turn it off and nothing special happened. After a few minutes working I have to wait a few seconds to use some tools. Changing exposure is not instant.

20 Messages

 • 

796 Points

Ugh, this is getting depressing.

5 Messages

 • 

188 Points

I tried to make a new catalog and it seems little bit faster. But it is not a miracle.

32 Messages

 • 

870 Points

After a few minutes working I have to wait a few seconds to use some tools.
Same here: At first glance, the new version seems to be faster. But after intensive work with many photos I quickly realize that nothing has changed. After X photos, Lightroom is slower and slower and needs to be restarted. I am frustrated!

Champion

 • 

2.2K Messages

 • 

37.4K Points

My previously well-performing quad-core system with 12GB memory is now exhibiting the same issue. After working on some images for a few minutes I start to see a slow-down in Develop controls response and even Library module scrolling slows down. Memory usage keeps climbing, but even with 5GB  "available" memory" showing I see a performance decrease. I'm also seeing intermittent image "tiling" after upgrading to the latest 375.86 Nvidia Graphics driver, which I did before the CC 2015.8 update. I'm going to drop back to the previous 368.86 driver version I was using and see if performance is better.

Champion

 • 

2.2K Messages

 • 

37.4K Points

With the Nvidia video driver rolled back to 368.86 LR CC 2015.8 is performing well and the same as with CC 2015.7. This is on Windows 7 with an i7-860 quad core CPU. My performance issue was due to the Nvidia driver update, which was made shortly before the CC 2015.8 update.

12 Messages

 • 

244 Points

I have the feeling it is a little bit better, but just a little bit. So waiting for a better update.

443 Messages

 • 

6.6K Points

I have found the same; with the older 368.86 NVidia driver (on my M2000 Quadro driver) everything in LR 2015.8 is snappier than with the latest 375.86 driver.

BUT everything in Win10 is also faster, so it is not just a LR problem, it is a problem with the latest driver and everything!

Bob Frost


Champion

 • 

2.2K Messages

 • 

37.4K Points

I generally never upgrade any driver unless there's a specific issue.......I made an exception this time and it came back  to bite me. I won't be doing that again!

150 Messages

 • 

2.9K Points

4 years ago

After working for few hours with this release. I can confidently say that the performance issues have NOT been resolved and I still need to restart lightroom every 5-10 minutes to get back to have a responsive experience like it is after a lightroom restart otherwise it is painfully slow.

Adobe might have improve something as it feels take longer now before the performance drop kicks in.

keep working on it please as it has been like that that for more than a year, what a flop...

here is my spec.

Lightroom version: CC 2015.8 [ 1099473 ]License: Creative Cloud
Operating system: Windows 10
Version: 10.0
Application architecture: x64
System architecture: x64
Logical processor count: 16
Processor speed: 3.0 GHz
Built-in memory: 65446.8 MB
Real memory available to Lightroom: 65446.8 MB
Real memory used by Lightroom: 827.2 MB (1.2%)
Virtual memory used by Lightroom: 791.7 MB
Memory cache size: 552.2 MB
Maximum thread count used by Camera Raw: 16
Camera Raw SIMD optimization: SSE2,AVX,AVX2
System DPI setting: 96 DPI
Desktop composition enabled: Yes
Displays: 1) 3840x2160
Input types: Multitouch: No, Integrated touch: No, Integrated pen: Yes, External touch: No, External pen: Yes, Keyboard: No

Graphics Processor Info: 
GeForce GTX 980 Ti/PCIe/SSE2

Check OpenGL support: Passed
Vendor: NVIDIA Corporation
Version: 3.3.0 NVIDIA 376.19
Renderer: GeForce GTX 980 Ti/PCIe/SSE2
LanguageVersion: 3.30 NVIDIA via Cg compiler


Application folder: C:\Program Files\Adobe\Adobe Lightroom
Library Path: L:\LR Catalog\LR 6 Catalog Full\LR 6 Catalog Full.lrcat
Settings Folder: C:\Users\User\AppData\Roaming\Adobe\Lightroom

Installed Plugins: 
1) Canon Tether Plugin
2) ColorChecker Passport
3) Export to Photomatix Pro
4) jb Search Replace Transfer
5) jf Metadata Wrangler
6) jf Snapshot on Export
7) Leica Tether Plugin
8) LR/Transporter
9) Nikon Tether Plugin
10) Stockboxphoto

Config.lua flags: None

32 Messages

 • 

870 Points

This is also exactly my experience with 2015.8 :-(

150 Messages

 • 

2.9K Points

4 years ago

if anyone at adobe reads this thread, I'm sure many of us including me will be happy to do some beta testing on our PCs if you send us some experimental versions to test for this issue.