teddyen's profile

1 Message

 • 

102 Points

Tue, Apr 18, 2017 8:27 PM

Closed

Lightroom: Very bad utilization of AMD Ryzen 1800X. Sluggish performance.

I recently upgraded from an Intel i5 2500K system to a AMD Ryzen 1800X-based machine.

I'm having a blast editing 4K content in Premiere, but Lightroom? It's actually slower on the new setup, and I see many people complaining about Lightroom's bad performance on CPUs with more than four cores. It's actually killing me, it's at times a nightmare to work with.

A CPU utilization of only 30% when rendering previews and exports is something I can live with although it seems like a total waste as it should be "easy" to adress, but the sluggishness during editing is horrible. I believe have set up everything correctly. I have, after all, worked with Lightroom since your very first release, and profesionally for the last four years.

I'm always rendering 1:1 previews. These are stored on a 500GB Samsung 850 EVO SSD, along with the catalog.
All my active raw files are stored on a 1TB PM961 M.2 drive, with sequential read speeds of 2700MB/s. I have set up a 50GB Camera Raw Cache, and installed Adobe CC on this drive as well.
Windows 10 is a fresh install, and on a separate SSD.

All drivers and fw/bios are up to date.

This system has no bottlenecks.

My system specs:
CPU: AMD Ryzen 1800X (8-core 16-thread)
RAM: G.Skill RipjawsV 64GB 3200MHz CL16 (@2666MHz for now)
GPU: MSI 1080Ti FE
SSD: PM961 M.2, Samsung 850 EVO and two Intel SSDs.
OS: Windows 10

Any suggestions?

Employee

 • 

1.7K Messages

 • 

32.4K Points

5 y ago

"A CPU utilization of only 30% when rendering previews"
You can consider breaking up your 1:1 previews building into 2 or 3 batches of photos (based on the folders or other criteria) and kick off the 1:1 previews building menu command for each batch at the same time. This allows multiple 1:1 preview building tasks running concurrently in the background. This pushes Lr to more fully utilize the compute resources available to you in your setup. Lightroom is doing this under the hood for you automatically in the case of export. The drawback is that when the compute resource is more fully utilized for the preview building/export, the interactive responsiveness of Lr might suffer a little bit. But for folks who can walk away from the desk while the concurrent preview building is running, it is a good workaround that is within customer's control.

"the sluggishness during editing is horrible"
Can you describe the sort of develop editing that you do that felts sluggish?

Champion

 • 

6K Messages

 • 

103.7K Points

5 y ago

Many users have reported severe performance problems running LR with more than 4 cores: https://feedback.photoshop.com/photoshop_family/topics/lightroom-clone-and-brush-tool-can-not-stress...

You could try restricting LR to running on 4 cores, as described here: https://feedback.photoshop.com/photoshop_family/topics/lightroom-clone-and-brush-tool-can-not-stress... .  That has helped some but not all.

Employee

 • 

1.7K Messages

 • 

32.4K Points

5 y ago

Assuming that you are running Lr CC 2015.10 (Lr 6.10), 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 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.

1 Message

 • 

62 Points

Thank you, Simon. I'm really not sure what this did for my R7 1800X system, but it managed to make lightroom at least somewhat usable. Before this, I wasn't even able to scroll through the library view without freezing for 5-10s at a time (even with all previews built) and the application would constantly become non-responsive in the develop module. Now the application is usable, but still janky.

 The strange thing is, the application's performance remained in its improved state after deleting the file and checking that the config.lua flags were not being loaded. 

2 Messages

 • 

82 Points

Hi All, 

I have been using the suggested Config.lua 'flag Develop.AdjustMaximumThreadCount = 0.51' for version 2015.10 & 2015.11 for a few months on a Ryzen 7 system with good results. Thanks Simon!

My Question is...For any one who has upgraded to 2015.12 Classic CC, have you now removed the flag or have kept it in place(it doesn't get removed as part of the LR Classic CC update.)

I will be doing my own testing too over the coming weeks and will report back. Curious to what others are experiencing as well. Would certainly welcome and apreciate Simon's advice on whether it is still advisable.. :o)

TIA

My System Spec for comparison:
Ryzen 7 1700x 8C/16T @ 3.9Ghz
48GB RAM @ 2800Mhz
NVMe SSD - System & Lightroom Catalog/Previews
SSD - Source RAW Files
12GB RAM Disk - Used for the RAW cache!
Monitor @ 1440p

Employee

 • 

1.7K Messages

 • 

32.4K Points

The config.lua flag will continue to work. You should try to test the new Lr Classic CC without the config.lua and see if you can achieve similar or better results. The best way to do that is just renaming the config.lua to say ~config.lua. You can rename the file back if you want to restore your old setup.

We are continuing working on the performance improvements in the coming releases to make the performance scale.

Principal Scientist, Adobe Lightroom

2 Messages

 • 

82 Points

Thanks for the swift feedback Simon. Probably been a busy day for you.

So far so good, very snappy, with the flag in place. Will try without tomorrow.

Edit to my original post: I did mean to say "For anyone who has upgraded upgraded to Lightroom Classic CC (v7.0)" not "2015.12 Classic CC"

2 Messages

 • 

70 Points

Same issues here on a very high end Ryzen 7 1700x system, woeful performance. This file helped quite a bit, but it's still not as good as it should be.