Copy link to clipboard
Copied
Desktop PC. I9-12900, 64GB memory, GPU is an Nvidia 4060TI. All the storage is on M.2 NVMe with images on an 8 TB SSD.
Images are nothing special – I see the same behavior whether it’s a 20 megapixel image or a 50 megapixel one.
I looked through several of the topics in here (some from older versions, some from LRC13) from other people having performance issues with Lightroom 13.X. Hopefully, I’ve missed something simple, but I didn’t see much to resolve the problems.
I have to add myself to the people having problems with slow, laggy, hanging operations in Lightroom 13.
I upgraded from the AMD GPU that worked OK with LRC 12 to the 4060 TI was because once I started using LRC 13, performance deteriorated. I thought throwing a more capable GPU at the problem would cure it. Didn’t work.
It’s not a problem as near as I can tell when doing normal, “adjust sliders in Develop” or “select a keyword” sort of adjustments. But when doing things like masks, particularly brush masks, the cursor just stops and hangs for up to several seconds, then resumes. It makes getting accurate selections more difficult because the cursor isn’t smooth. Zooming to 100% to make more accurate selections makes it worse.
Similar behavior can happen when using the Lens Blur – the cursor hangs when doing Blur or Focus and when making adjustments in Visualize Depth. I also see it occasionally when doing content-aware remove, but I only use that very rarely in Lightroom.
I was also hoping for faster exports, faster 1:1 previews, and so on. Not much happened there either, but I can live with that if I can get rid of the hanging and lag.
I don’t see this behavior with any of the tools in Photoshop.
I don’t see the behavior in Topaz Photo AI, which runs perceptibly faster with the 4060 than with the old GPU.
I’ve done the “standard” things I believe. Tried no graphics acceleration – just made everything slower. And the partial acceleration. And full acceleration. The lag, hang and such is always there.
I disabled the onboard GPU.
I opened the Nvidia control panel and added both Lightroom and Photoshop in there.
I've made sure it' susing the durrent drivers. I've tried both the studio and game-ready drivers.
Are there settings for the GPU in the Nvidia control panel that can be configured to make Lightroom (and Photoshop, but mostly Lightroom) perform significantly better?
Are there other things I should try that are likely to address the problem? System configuration? Something in Lightroom configuration?
Has Adobe said anything about being aware of the problem and trying to correct it?
Copy link to clipboard
Copied
Same issue here... 10900k, 2080Ti.
Copy link to clipboard
Copied
So I bit the bullet and downloaded and registered Nvidia's cr*pware - GEForce Experience - and clicked the "optimize" button for Lightroom Classic (under Games&Apps in the Home menu) and have been running error free for a couple days even under heavy edits (multiple masks, etc.). Not sure if this is a fix or just temporary luck. Maybe the ware ain't so crap*y after all.
Copy link to clipboard
Copied
Might as well give it a try - nothing else has worked...
Copy link to clipboard
Copied
Please, report back if the performance is still good or if it was just a placebo.
Copy link to clipboard
Copied
Still stable. No crashes since I optimized it. Occassionally laggy in develop mode with masks, but much less frequent than before. Not sure what it is doing to "optimize" the processor, and have not taken the time to research it. The only change I can see in LR is the Use Graphics Processor check box (Edit>Preferences>Performance) now says "Custom" instead of Auto or Off, but no indication what the Custom settings are (and I don't want to mess with it to figure it out until/unless my rig starts acting up again).
Copy link to clipboard
Copied
I'm trying Microsoft driver now, not too lagy like latest from nvidia. LR looks stable, use GP - custom.
Copy link to clipboard
Copied
what about masking tools ??
Copy link to clipboard
Copied
Where did you get the Microsoft version of the current driver for the 4060 TI?
And, which driver - the Game-ready version or the Studio version are people using? Has anyone seen any difference between them (in my testing, I HAVEN'T, but that doesn't mean there isn't)...
Copy link to clipboard
Copied
A shot in the dark.. do you, by any chance, use ISLC tool (Intelligent standby list cleaner)?
Copy link to clipboard
Copied
I'm not sure what the ISLC is or does. I'll have to look.
As far as any perceptible improvement with the "Microsoft" Nvidia drivers, I haven't found anything that specifically says they're for Microsoft. I AM using the current version of Nvidia Studio drivers and they're either JUST as bad as previously or so close that the difference is negligible. Today, doing some slight to moderate (in my mind) generative fill for removing distractions on an image resulted in a very quick decline in performance with lag time often exceeding 4-5 seconds while the mouse hung.
Copy link to clipboard
Copied
Works slightly better.
Copy link to clipboard
Copied
Some comments disappeared and now my reaction is under the wrong reply. Looks like someone is making a mess here. 😄
Copy link to clipboard
Copied
I'm not sure where or how this topic got to the state it's in, but my system says there are at LEAST 5 new posts from today... I'm not sure where they are...
So far, NOTHING I've done has had any positive effect on the poor Lightroom performance that happens whenever I run Lightroom for any length of time.
I've found some topics in OTHER discussion groups, specifically targeting the 4060TI as the source of performance issues, some IN Lightroom and some that appeared to be general complaints about the 4060TI having all manner of performance issues.
I don't know if there IS a problem with Lightroom Classic and the 4060TI, but once I'm able I'm going to pull the card out and install the old AMD 5700XT and see if that older, slower card DOESN'T have the same problems...
Copy link to clipboard
Copied
I have the exact same problem, but mainly in Adobe Camera Raw and I use the RTX 4070...
So I have no idea what the problem is, I really hope it gets resolved one day
Copy link to clipboard
Copied
Copy link to clipboard
Copied
I thought I am alone here. When I go on the forum I cant see any posts.Thus I am replying to this thread via email lmao.
By @Julius90
What URL?
Copy link to clipboard
Copied
Try turn it off. 🙂
Copy link to clipboard
Copied
Very early thing to try. I slowed everything down.
Copy link to clipboard
Copied
Hey, I found the answer. What helped for me was this:
Just turn of HAGC if it's on under Windows settings / Display / Graphics.
I hope this will help for more of you.
No more lag.
Copy link to clipboard
Copied
Hey, I found the answer. What helped for me was this:
Just turn of HAGC if it's on under Windows settings / Display / Graphics.
I hope this will help for more of you.
No more lag.
By @Julius90
Looking back at the earlier replys, I do not see thtat you posted what GPU you have, other than NVIDIA. Using the Internet to see what Hardware Accelerated GPU Scheduling is, I see an old MC document that makes one possibly important point, the GPU must be able to support that. Mind you I would think Windows OS would prevent that if that was the case. Specifically "GPUs that have the necessary hardware, combined with a WDDMv2.7 driver that exposes this support to Windows"
Naturally as this goes back to early Windows 10, any GPU produced after that should be good to go. So, what GPU??
hmm, this article, and this one covers Windows 11, states that this feature by default is off.
But I do not remember turning it on (my rig it is on, no issues), /followup/ it appears some GPU driver installs might turn that on.:
Speaking of GPU support for HAG, the above article states:
"One caveat is that HAG only works with newer video cards. So, for Windows 11 to even let you switch it on and off you’ll need at least a Nvidia RTX 1000 or AMD 5600 series or later graphics card."
That article also states HAG might not provide much improvement. And it states HAG appears to be hit or miss (might work, might not)
Obviously members can turn this off and on to test. I would not think testing would be a danger.
Copy link to clipboard
Copied
Already off here.