Copy link to clipboard
Copied
This was posted on a similar thread where a Mac user has experienced the same issues, but I have been asked to open a new discussion as my OS is Windows 11.
My PC is well above LR Classic spec, but since upgrading to 13.2 all actions have become far slower than previous versions of LR Classic.
For instance, sliders in develop, which were previously instant now lag, with no visible preview for several seconds.
Intel i5-9600K CPU is approaching 100% whereas it rarely did pre v 13, little disc activity, 2GB of my 16GB RAM is free.
Simple activities are now painfully slow, even dragging the cropping tool is not always behaving in real-time, which makes it unusable, suddenly jumping to a small crop than required.
Very frustrating when it was working so well. No apparent background activities showing.
I have increased and cleared the cache.
It seems slightly better since I disabled the few plug-ins I have, but not spritely any more.
All catalogues and previews are on M2 SSD, original RAW photos on SATA SSD.
Why the change in responsiveness and usability Adobe?
SysInfo Below: -
Copy link to clipboard
Copied
Can you post a screenshot of LrC /preferences/performance/
I am curious about two things
1: The apparent inability to provide much GPU support, might be the old GPU, might be the VRAM (some have issues below 4GB despite's LrC System Requirements posted by Adobe)
Graphics Processor Info:
DirectX: NVIDIA GeForce GTX 1060 3GB (31.0.15.5161)
Init State: GPU for Image Processing supported by default
User Preference: Auto
And I have a suspicion that the following Adobe document may be of interest, especially Solution 2, thinking LrC might be reading the GPU info wrong (did you previously get Graphics acceleration?)
2. Location and amount of Camera RAW CACHE.
Copy link to clipboard
Copied
Thank you for the link.
No issues with GPU in the past, that is the correct card and it is on auto, no errors showing. Lastest Nvidia drivers too. I can also see that being used when I have Task Manager open.
I'll have a play with the settings over the weekend and get some screenshots.
Copy link to clipboard
Copied
Also
Library Path: D:\All Photos\Lightroom\Andy's Photo Catalogue\Andy's Pre-2017 Photo Catalogue v13.lrcat
that I see is
catalogues and previews are on M2 SSD
Normally I would ask as to how much free space in percent, looking for at least 20%, some say 25% free. But I think in this case, how large a drive, how much used space? As my inquiry about Camera RAW CACHE might get involved.
Copy link to clipboard
Copied
I'm away from the PC for a while, and can' recall the exact disc configuration but I know there is plenty of space.
I'll check up further details over the weekend.
Thanks.
Copy link to clipboard
Copied
Drives:
C: Corsair MP510 Capacity 892GB 368 GB Free (41%) (M.2 PCI SSD)
D: WD 3TB HDD 630 GB Free (23%)
E: Spanned 2x WD 1TB (873GB Free 47%) (M.2 PCI SSD)
Note, I did the SysInfo dump whilst working on an older catalogue which is still on the platter HDD, but the problems reared their head on a cataolgue stored, with previews, on the C: Drive which is the fasted of the SSD drives.
RAW caches also on the fasted C: drive.
GPU
See below. It is a Nvidia GeForce GTX 1060 3GB.
Initially on Auto, but Nvidia recommended a different setting, so I "optimised" this evening, and the new custom setting is shown, below, on the bottom panel. However, "use GPU for image processing" is, after a retart, now greyed out...
FOr infor, there is a short video of Task Manager - all I am doing in LRc is moving teh Highlights slider up and down. The image is a 20MB RAW (Sony ARW) 5472x2648 colour image - no masks or AI adaptations.
Many thanks.
Copy link to clipboard
Copied
About that custom setting and some options appearing to be grayed out. I have attached a video showing how that might be a bit confusing, and you might try clicking on the options. And notice that while your option Use GPU for Display is gray, it is also checked, so that option is in effect, you just cannot unchecked it while the next option use GPU for Image Processing is selected. It also looks like you can go one more deep and Use GPU for Export, however, some members with old GPU's may have had issues with that (you would need to test)
Copy link to clipboard
Copied
The "Use GPU for Image Processing" is now greyed out.
Oddly, after turning ff GPU acceleration in Lightroom, it prompted me to "enmable" it, which I did. Having done so, this image processing option was ticked by LR, but, on restart, it was greyed out again...
Looking at the Adobe website it seems that the updates may have leapfrogged my Graphics card spec as the recommended VRAM is now 4GB (page dated October 2023) but I have 3GB.
Time for a little shopping, perhaps?
Copy link to clipboard
Copied
D: WD 3TB HDD 630 GB Free (23%)
Getting a bit short on free space for the catalog(s)
Copy link to clipboard
Copied
My current catalogues are on C. The older ones, on D aren't being added to, so there is plenty of room.
Copy link to clipboard
Copied
RAW caches also on the fasted C: drive
That may or may not be an issue. Problem is with Windows, not with MAC, and the Windows Paging file. The Paging file and the Adobe Camerra RAW CACHE (the CACHE used by LrC) can conflict with read/wrights on the hard drive. This would be a performance hit, it would only be in Develop, and the performance hit ma be small. An LrC update would not change this for the better or worse unless something really stepped on the use of CACHE
Yes, both the catalog location, and the CACHE location can take advantage of being on the fastest hard drive (the photos could care less)
Copy link to clipboard
Copied
I will check again, later.
Again, I am not sure why the update would have significantly changed the use of the Virtual memory or LR Cache.
Copy link to clipboard
Copied
I have a user defined Virtual Memory of 12-16GB on C: drive, so there is still plenty of room.
Copy link to clipboard
Copied
Microsoft recommends that virtual memory be set at no less than 1.5 times and no more than 3 times the amount of RAM on the computer. In your case the minimum should be 24GB. I recommend that tou increase yours to at least 24GB to see if it helps.
Copy link to clipboard
Copied
Issue or consideration for optimizing LrC was not how much you allow the Windows Paging file to get, that particular virtual memory, but the location of the Adobe Camera RAW CACHE in relation to the Windows Paging file. With a optimization recommendation when possible to not locate both on the same hard drive. Typically let the Windows Paging file reside on C drive as is default, typically let Windows decide on Windows Paging file size, and place the Adobe Camera RAW CACHE on a different drive. The two files can compete with read/wrights on the hard drive. But if you do not have another drive, then this tip provides a small performance improvement that you may choose to ignore, and the hoped for performance improvement might be offset if you have to move it to a slow drive (in that case, leave on C).
LrC will use both the Windows Paging file (when? a big question) and when in develop module, the Adobe Camera RAW CACHE file.
Upon updates, and upgrades, when Adobe adds features like AI, the use of the Windows Paging file and the Adobe Camera RAW CACHE might get increased (but Adobe does not share that sort of info to us common customers)
Copy link to clipboard
Copied
Possible Issue identified - LR was eating 50-70% of CPU when I was doing nothing... So what was going on?
It looks like the background task of "Saving XMP" is a possible culprit, on pausing, the CPU Usage drops to <5% (background tasks are only visible if you click on the IDentity Plate (Top left - often your name, unless you have changed the defaults.)
I wonder whether 13.2 is not handling this background task as well so it is interfering with edits and image handling?
More testing required, but it does seem that there is a lag when making edits when the XMP saving option is live, which is not apparent when paused.
Copy link to clipboard
Copied
Lightroom 13.2 classic seems to have settled down, but it still has some moments when it hesitates and some higher than expected cpu usage. I think it may have been a wholesale XMP rewrite? Perhaps the handling of background tasks is not working as smoothly.?
Meanwhile, I have ruled out RAM as a problem by doubling it to 32GB.
I have also ruled out GPU problems as I have upgraded to a GTX 4060 8GB.
LrC now fully using GPU. By way of comparison, an AI Noise reduction which took 3' 45" with my 1060 3gb took just 20" with the new graphics card!