Performance regression browsing images on 4k monitor

[RH_1234]

I've been using Lightroom Classic for more than 12 years. I've got a big workstation with lots of CPU and GPU. Lightroom Classic worked great last year on this computer. Now it takes approximately 0.7 seconds to change photos in Library mode. I narrowed it down to the fact that my monitor is in 4k resolution. If I drag Lightroom to my second monitor (1440p resolution) the image switching performance is back to normal. If I lower the resolution of my 4k display to 1440p or lower, the performance is back to normal. This computer used to run Lightroom normally on this same display with all the same settings (same preview size, image import settings, etc). This is a performance regression and it makes Lightroom essentially unusable for my workflow culling and managing a lot of images from my shoots.

I'm on windows 11 23H2. Everything is fully updated (Windows 11.0.22631, NVIDIA graphics drivers 566.03, Lightroom Classic 14.0.1).

System Info is attached.

[Moved from ‘Bugs’ to ‘Discussions’ by moderator, according to forum rules.]

[fani kurti]

Wow! Crazy thing. Enabling the HDR made a huge difference in Library, Grid and Develop modules. They should check this by default.

I was struggling with the overall slow interface of version 14. I was thinking of rolling back to version 12.5 but now i think i can work comfortably with version 14 as well.

This is huge for me!

Thank you very much! 

About the Exporting.... i  will keep GPU off for now and hope that i will find a solution one day, but it is not a deal breaker at this point. 

Thanks again!

[johnrellis]

Moderators, @Rikk Flohr: Photography: Please merge with this thread:

https://community.adobe.com/t5/lightroom-classic-discussions/performance-regression-browsing-images-...

A number of people have reported that enabled Preferences > Performance > Enable HDR In Library fixes severe performance problems, even though they're not doing HDR editing. It would be good to collect all those reports in one place.

[Ian Lyons]

@johnrellis 

I  reported it internally on Monday (11 November).