Lightroom classic extremely slow on new powerful PC

[jasonw2420467]

Hi all,

Hoping someone can help me.  I have an Adobe plan with Lightroom & Photoshop included.  Both have worked fine for years, however I now have a new PC (much more powerful than my last) & whilst Photoshop still works, Lightroom Classic is being very slow to launch (stuck ages on "reading preferences" on the splash screen, then any slider I click on in the development module is taking 2-3 minutes to ungrey itself out.

Importing images is lightning quick, as is rendering 1:1 previews.  I've increased my cache & tweaked the GPU accelerator - no difference on either change.

I've had to revert back to an old copy of LR5 which doesn't support the raw files I'm currently creating, meaning a very manual workflow including a raw to dng converter.

A family member who's very techy worked with me for 2 hours on the weekend looking for solutions & doing checks - we cannot find anything.

Can anyone suggest anything or can Adobe advise if this is a known issue?

I'm using Win11

Local disk is 15% used with 781gb free

CPU is Intel(R) UHD Graphics 770

Graphics card is NVDIA GeForce RTX 5070 Ti

RAM 64GB 

I am desperate to come away from the LR5 solution as it lacks so much Vs the latest classic version.

[DS256]

Unfortunately not uncommon. You may want to check out the Lightroom Queen Performance posts.

Have you run Task Manager when you experience slow performance to see what resources may be maxed out?

[jasonw2420467]

Thanks - I'll look over that.  Yes the task manager isn't revealing anything, it's not using much up at all, 5% I think it was.

[DS256]

Don't forget there are 3 resources to check; CPU, Memory and Disk. For example, Windows Indexing may be hogging disk IO.

[jasonw2420467]

I'm not entirely sure what to look for but hopefully this helps to rule things out?

[GoldingD]

CPU is Intel(R) UHD Graphics 770

Actually that is the integrated video controll within your CPU. 

Graphics card is NVDIA GeForce RTX 5070 Ti

And from your GPU, I assume this is a desktop computer or perhaps a workstation. As such, the integrated video controller probably has no influence into your LrC. Had this been a laptop, perhaps a conflict could occur, and perhaps deactivating the integrated video controller driver would help, but that is rare.

__________________________________________________

1. Can you post a screenshot of LrC /Preferences/Performance/
2. Please post your System Information as Lightroom Classic (LrC) reports it. In LrC click on Help, then System Info, then Copy. Paste that information into a reply. Please present all information from first line down to and including Plug-in Info. Info after Plug-in info can be cut out as that is just so much dead space to us non-Techs and it takes up vast amounts of scroll space making the reply less readable and less likely that others will bother with your post. Also large amounts of text in a post also render the Translate function inoperable.

[Per Berntsen]

CPU is Intel(R) UHD Graphics 770

Actually that is the integrated video controll within your CPU. 

Graphics card is NVDIA GeForce RTX 5070 Ti

And from your GPU, I assume this is a desktop computer or perhaps a workstation. As such, the integrated video controller probably has no influence into your LrC. Had this been a laptop, perhaps a conflict could occur, and perhaps deactivating the integrated video controller driver would help, but that is rare.

By @GoldingD

I had this happen on a new desktop computer, and disabling the integrated GPU fixed it.

@jasonw2420467 

Open the Windows Device manager, right click the UHD Graphics and choose Disable device.

Relaunch LrC if it's running. Does that fix the issue?

[jasonw2420467]

I can no longer get back into windows since disabling this device. How can I reverse that change please? 

[GoldingD]

Verify that your monitor is connected to your GPU, and not accidentally connected to the motherboards port.

Also, when did access to Windows fail, just after the change in the device settings? Or after a restart of the computer, or after a shutdown then turning back on the computer

Ahh, and when you disabled the device, did you disable the integrated video control, or the discrete GPU. If you accidentally deactivated the NVIDIA, then that is the issue, You could try changing the connection between monitor and computer (inquired upon in first sentence) connecting to the video port on the motherboard, that would communicate to the integrated video control, hopefully you could go back into the device manager and turn the GPU back on. (or download and re-install the NVIDIA driver)

[jasonw2420467]

So I did the disable device piece, the screen went black but everything was powered on still. Nothing was responding so I did a restart and on restarting it seemed to get part way in, the windows logo was there but the circle under it wasn't a full circle spinning.

Before the device disabling thing, everything was ok

[jasonw2420467]

The monitor was connected to the top port (1st image) but I've now changed it to the first port on the horizontal row (2nd pic) 

 

 

[GoldingD]

Ah, in that first picture, those ports appear to be the ones off the motherboard, both that HDMI and that DP ports, as well as the USB ports, etc.

In the second picture, that would be the GPU card, apparently with four three DP ports, and one HDMI port, that is where the connection should have been

Does your computer now work?

Also, what is that HDMI port connected to? A second port on the back of your monitor? 

Also, are you using HDMI or DP, or both? Perhaps a limitation to HDMI for the monitor? If the monitor supports DP, then many advise using DP over HDMI. If the monitor only supports HDMI, then a future upgrade consideration.

[jasonw2420467]

Thanks for the detailed steps there.  Here is what you said would be helpful - hopefully it shows something...

1) performance tab in LR

2) the system info as LR sees it:-

Lightroom Classic version: 14.2 [ 202502071718-3869eef7 ]
License: Creative Cloud
Language setting: en
Operating system: Windows 11 - Home Premium Edition
Version: 11.0.26100
Application architecture: x64
System architecture: x64
Logical processor count: 28
Processor speed: 3.4GHz
SqLite Version: 3.36.0
CPU Utilisation: 0.0%
Power Source: Plugged In
Built-in memory: 65253.2 MB
Dedicated GPU memory used by Lightroom: 157.0MB / 15907.0MB (0%)
Real memory available to Lightroom: 65253.2 MB
Real memory used by Lightroom: 1006.3 MB (1.5%)
Virtual memory used by Lightroom: 1187.5 MB
GDI objects count: 908
USER objects count: 2682
Process handles count: 3390
Memory cache size: 0.0MB
Internal Camera Raw version: 17.2 [ 2155 ]
Maximum thread count used by Camera Raw: 5
Camera Raw SIMD optimization: SSE2,AVX,AVX2
Camera Raw virtual memory: 1MB / 32626MB (0%)
Camera Raw real memory: 2MB / 65253MB (0%)

Cache1:
NT- RAM:0.0MB, VRAM:0.0MB, Combined:0.0MB

Cache2:
m:0.0MB, n:0.0MB

U-main: 99.0MB

System DPI setting: 96 DPI
Desktop composition enabled: Yes
Standard Preview Size: 1440 pixels
Displays: 1) 1920x1080
Input types: Multitouch: No, Integrated touch: No, Integrated pen: No, External touch: No, External pen: No, Keyboard: No

Graphics Processor Info:
DirectX: NVIDIA GeForce RTX 5070 Ti (32.0.15.7602)
Init State: GPU for Export supported by default
User Preference: GPU for Image Processing Enabled
Enable HDR in Library: OFF

Application folder: C:\Program Files\Adobe\Adobe Lightroom Classic
Library Path: C:\Users\wells\Pictures\LR catalog (new classic - not LR5)\LR catalog (new classic - not LR5).lrcat
Settings Folder: C:\Users\wells\AppData\Roaming\Adobe\Lightroom

[jasonw2420467 · Accepted solution]

Well that was some scary evening.  I've ended up reinstalling windows 11, but guess what, the latest version of LR Classic is now lightning pace to load up & to develop any image - maybe it was something the people I brought it from put on or how it was setup but hey ho.

Guys - thank you for helping me over the last 24 hours, although I've no idea what's sorted it, I'm just over the moon I can get back to my old workflow but on my new setup.  Btw, I had a new hdmi cable today & I think I'd inadverntly put in the wrong port, I don't think that was the source of the problem but it didn't help me earlier that's for sure