Highlighted

LR CC VERY slow on hi-end PC

Explorer ,
Apr 24, 2017

Copy link to clipboard

Copied

My PC: i7 6700k, 32GB DDR, Samsung SSD, GTX 1070 Windows 10

Lightroom is very slow at basic tasks like select images, change module, write caption title etc.

Can take up to 10 seconds just to select a few images. small jpgs as well as hires raws. LR freezes for some seconds (not responding).

What I have tried:

uncheck/check gpu acc.

reset preferences.

removed all plugins

disabled all plugins

uninstall and reinstall LR

made a new catalog with just 130 images. Same response as catalog with 100k images.

When browsing images, the cpu usage goes up to 10-15%

It's been like this since last fall when I built this PC. On my macbook pro 2011 it is just regular slow. Not ridiculous slow like this.

But tasks like editing images with the sliders in dev module, import and export seems to run like normal.

Ok. So I ran the benchmark. First i got only 3800 (total. the 11k number you refer to is cpu only. I got 11500 there). And noticed that the 2D performance was really low. like GT 630 low.

So I reinstalled the graphics driver, and what do you know, the graphics performance went up to over GTX980 scores. (5800 points total)

So that fixed Lightrooms lag.

I didn't think of reinstalling the graphics driver since it was only LR that lagged. And I have been updating the graphics drivers several times without noticing any improvement in LR.

Views

8.9K

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

LR CC VERY slow on hi-end PC

Explorer ,
Apr 24, 2017

Copy link to clipboard

Copied

My PC: i7 6700k, 32GB DDR, Samsung SSD, GTX 1070 Windows 10

Lightroom is very slow at basic tasks like select images, change module, write caption title etc.

Can take up to 10 seconds just to select a few images. small jpgs as well as hires raws. LR freezes for some seconds (not responding).

What I have tried:

uncheck/check gpu acc.

reset preferences.

removed all plugins

disabled all plugins

uninstall and reinstall LR

made a new catalog with just 130 images. Same response as catalog with 100k images.

When browsing images, the cpu usage goes up to 10-15%

It's been like this since last fall when I built this PC. On my macbook pro 2011 it is just regular slow. Not ridiculous slow like this.

But tasks like editing images with the sliders in dev module, import and export seems to run like normal.

Ok. So I ran the benchmark. First i got only 3800 (total. the 11k number you refer to is cpu only. I got 11500 there). And noticed that the 2D performance was really low. like GT 630 low.

So I reinstalled the graphics driver, and what do you know, the graphics performance went up to over GTX980 scores. (5800 points total)

So that fixed Lightrooms lag.

I didn't think of reinstalling the graphics driver since it was only LR that lagged. And I have been updating the graphics drivers several times without noticing any improvement in LR.

Views

8.9K

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Apr 24, 2017 0
Adobe Employee ,
Apr 24, 2017

Copy link to clipboard

Copied

Can you give us a complete description of your storage attached to this machine?

Where are images stored?

Where is the catalog stored?

Where is the Lightroom program file stored?

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 24, 2017 1
Explorer ,
Apr 24, 2017

Copy link to clipboard

Copied

ah yeah sorry. all on SSD via Sata3

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 24, 2017 0
Adobe Employee ,
Apr 24, 2017

Copy link to clipboard

Copied

All on the same SSD?

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 24, 2017 0
Explorer ,
Apr 24, 2017

Copy link to clipboard

Copied

yes.

and in another scenario I have the pictures on internal HDD. No difference at all. (LR catalog etc on SSD)

I don't notice any difference on editing/browsing images that are on a SSD or a HDD.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 24, 2017 0
Adobe Employee ,
Apr 24, 2017

Copy link to clipboard

Copied

SSD Capacity?

Free Space?

Any network assets attached?

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 24, 2017 0
Explorer ,
Apr 24, 2017

Copy link to clipboard

Copied

500gb. 130gb free. no network.

LR cache set to 60GB

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 24, 2017 0
Adobe Community Professional ,
Apr 24, 2017

Copy link to clipboard

Copied

Makes sure all background activities are 'Paused.'

This user with a very similar system is seeing very good LR performance: Processing Large Files

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 24, 2017 0
Explorer ,
Apr 24, 2017

Copy link to clipboard

Copied

all of them are unchecked. the problem isn't processing image. i.e. sliders in develop module. but basically everything else. doesn't matter the image size.

I will make a screen video of the issues when I find out how to do that.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 24, 2017 0
Adobe Community Professional ,
Apr 24, 2017

Copy link to clipboard

Copied

What LR version are you using? Help> System Info?

Try changing the Library module Metadata panel to the 'Default' setting.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 24, 2017 0
Explorer ,
Apr 24, 2017

Copy link to clipboard

Copied

Latest CC. it is on default

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 24, 2017 0
Adobe Community Professional ,
Apr 24, 2017

Copy link to clipboard

Copied

So just to confirm you are running LR CC 2015.10 and tried 'Use Graphics Processor' unchecked in Preferences,  reset LR Preferences, created a new catalog and imported 130 images into it, installed/reinstalled LR, removed all plugins, and set the Metadata panel to 'Default' setting. After making these changes the Library module functions remain persistently slow, but the Develop module controls function normally.

Two more things to try:

1) Change the monitor profile to sRGB if using a standard gamut display or Adobe RGB if using a wide gamut display:

https://www.lightroomqueen.com/articles-page/how-do-i-change-my-monitor-profile-to-check-whether-its...

2) Update your graphics driver: nVidia drivers

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 24, 2017 1
Explorer ,
Apr 25, 2017

Copy link to clipboard

Copied

Can't say that it improved. maybe 5-10% improvement.

But I have been calibrating my display since I got this. And graphics drivers have been updated several times since last fall. Haven't noticed any changes between that.

So what else do you suggest? But a mac? It went relatively smoothly on my mac mini 2012

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 25, 2017 0
Adobe Community Professional ,
Apr 25, 2017

Copy link to clipboard

Copied

As I mentioned in my first reply, This user with a very similar system is seeing very good LR performance:

Processing Large Files

I also don't think this is an issue with the type of system you're using since you say,  "sliders in dev module, import and export seems to run like normal."  Most performance complaints concern the Develop module or simply ALL of LR's functions.

We're missing a key piece of information to solve this issue. I'm suspect of the image files you're processing, but you say "On my macbook pro 2011 it is just regular slow. Not ridiculous slow like this." I assume you mean using the exact same image files, correct? BTW- What type of image files are you processing that have this issue? I suggest uploading a few of the files with the issue to Dropbox for examination.

Since you say "It's been like this since last fall when I built this PC" you may have a basic system configuration issue. You can download and run the PassMark Performance Test,which has a 30-day free trial period:

PassMark PerformanceTest - PC benchmark software

You should achieve an 'Average CPU Mark' score of ~11,000:

PassMark - Intel Core i7-6700K @ 4.00GHz - Price performance comparison

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 25, 2017 0
Explorer ,
Apr 25, 2017

Copy link to clipboard

Copied

I made a screencap. free version only limited to 3 minutes. At the end I was going to enter text in the description tab, but LR didn't register the mouse click, so it started doing actions based on the letter I typed. A common scenario for me. I was writing "very slow", and LR started doing commands based on those letters.

does this look like normal LR perfomance? Lightroom windows - YouTube

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 25, 2017 0
Explorer ,
Apr 25, 2017

Copy link to clipboard

Copied

And I would like to add that LR is the only app that shows any slowness (well, except from Premiere lagging sometimes. The Adobe lag as I like to call it).

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 25, 2017 0
Adobe Community Professional ,
Apr 25, 2017

Copy link to clipboard

Copied

This is definitely not normal behavior for ANY system. It appears you have a resource bottle-neck somewhere. I suggest running the following benchmark test and check the CPU, Disk, and Memory performance numbers:

PassMark PerformanceTest - PC benchmark software

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 25, 2017 0
Explorer ,
Apr 27, 2017

Copy link to clipboard

Copied

Ok. So I ran the benchmark. First i got only 3800 (total. the 11k number you refer to is cpu only. I got 11500 there). And noticed that the 2D performance was really low. like GT 630 low.

So I reinstalled the graphics driver, and what do you know, the graphics performance went up to over GTX980 scores. (5800 points total)

So that fixed Lightrooms lag.

I didn't think of reinstalling the graphics driver since it was only LR that lagged. And I have been updating the graphics drivers several times without noticing any improvement in LR.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 27, 2017 0
Adobe Employee ,
Apr 27, 2017

Copy link to clipboard

Copied

Does that take care of your open Lightroom issues, Tor?

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 27, 2017 0
Explorer ,
Apr 27, 2017

Copy link to clipboard

Copied

It seems like LR is back to its normal slowness. So yeah, it did take care of my Lightroom issues.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 27, 2017 0
Adobe Employee ,
Apr 27, 2017

Copy link to clipboard

Copied

Good to hear. We'll work on 'normal slowness' next.  Thanks for your help and a shout out to TRSHANER!

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 27, 2017 2
Advocate ,
Apr 27, 2017

Copy link to clipboard

Copied

Thanks indeed to trstraner for the info about the Performance test. I didn't know what to expect of my homebuilt computer, except that it ought to be fastish, and I don't have any real performance problems with LR (only the slowdown with time).

For the Record, my test results were:-

Passmark     6246

cpu             15999

2D                 990

3D                4135

Memory        3041

Disk            14184

The hardware is i7-5930K cpu, M2000 Quadro, Samsung 860 ssd, 32GB ram.

Bob F.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 27, 2017 0
Adobe Community Professional ,
Apr 27, 2017

Copy link to clipboard

Copied

Tiboine  wrote

So that fixed Lightrooms lag.

I didn't think of reinstalling the graphics driver since it was only LR that lagged. And I have been updating the graphics drivers several times without noticing any improvement in LR.

Good to hear reinstalling the graphics drivers resolved the issue. To help others that land here with the same issue did you do anything differently this time compared to your previous updating of the graphics drivers? A graphics driver reinstallation should include uninstalling all of the current Nvidia named drivers using Windows Programs and Features, selecting 'Custom' installation setting with the new driver, and then checking 'Clean Install,' which resets the Nvidia Control Panel Preferences to the default settings.

Concerning the "normal slowness" I suggest going through trouble-shooting process again. Any changes you made previously were "masked" by the graphics driver issue so no way of telling if they helped. This would include creating a new catalog and importing some image files for testing, changing the display profile to sRGB or Adobe RGB, and resetting the Preferences file again.

Most all of the "unfixable" performance issues are with systems that use a 6 or more core processor. You have an i7-6700K quad-core system. We know at least one user is experiencing good performance with a very similar system using 42 Megapixel raw files and a 4K (3840x2160) display. What camera model files and display(s) are you using? This has the largest effect on LR's performance than any other factor!

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 27, 2017 0
Adobe Community Professional ,
Apr 27, 2017

Copy link to clipboard

Copied

Thanks Bob, you're one of the few people reporting in the forums that does NOT have LR issues using a 6-core processor system.

For comparison my much more modest i7-860 quad-core, Nvidia Quadro 600, 12GB, SSD system has no real issues processing 21 Mpixel 5D MKII raw files using a single 2560x1440 display. I've also done some testing using 50 Mpixel 5D MKIV raw files with very little difference in LR's performance noted. I do sometimes see the slowdown over time inside LR, but it's unpredictable.

Here are my PassMark results for comparison:

                     Frost   Shaner

Passmark     6246   2316

CPU           15999   5154

2D                  990     537

3D                4135     776

Memory        3041   1758

Disk            14184   2385

Percentile                   58% World Average

Quite a difference! What camera model files and display(s) are you using?

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 27, 2017 0
Explorer ,
Apr 28, 2017

Copy link to clipboard

Copied

The difference I did now was to uninstall the driver instead of just updating it.

Updating the driver didn't seem to have any effect. I have updated the graphics driver several times this year without LR caring about that.

and for the normal slowness, I'll just refer to google https://www.google.no/search?q=lightroom+slow&oq=lightroom+slow&aqs=chrome..69i57j69i61l2j0l3.2716j0...

Lightroom in the last iterations have never felt snappy. And as many other people have discovered, there is a diminishing return. faster PC spec doesn't translate into faster LR.

Last year I had a mac mini 2012 2.6ghz 16GB of ram and fusion drive. LR doesn't feel any faster now with my current spec.

And as for the "use graphics processor" option. Everywhere I read they say to turn it off to increase performance. Even Adobe reps says that. Why have it there to begin with?

in premiere there is a real performance boost when using the GPU to render instead of the cpu. Couldn't the engineers put that same engine into lightroom?

Anyway, this is over my pay grade, so I don't really need an answer to this as there is nothing I can do about it. But just putting it out here.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 28, 2017 0
Adobe Community Professional ,
Apr 28, 2017

Copy link to clipboard

Copied

I understand–At least we got you back to "normal slowness." From the posted PassMark results system and yours have about 2x more performance than mine. Bob and I have have no major issues (gradual slow-down with time), but you do. Go figure! Hopefully performance will be improved in a future LR release that better utilizes system resources.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 28, 2017 0
Adobe Community Professional ,
Apr 28, 2017

Copy link to clipboard

Copied

Lightroom in the last iterations have never felt snappy. And as many other people have discovered, there is a diminishing return. faster PC spec doesn't translate into faster LR.

I agree with that. I have two systems, one high-end and one midrange, and Lightroom is actually a tad faster with the latter.

There is ridiculously slow, and there is workable. A lot of people say there's no problem. My own experience (confirmed by what I've been reading), is that Lightroom has never been truly instant. There is always this little, annoying delay. How much it bothers you, depends on circumstances.

I've begun to suspect that this is just the downside of parametric editing. A new adjustment doesn't pick up where you left - instead it pushes all the other previous adjustments ahead of it in a longer and longer queue.

If one single problem can be separated, it seems to me to be reading from the caches (ACR cache or Previews). Why does it always take at least a half second (or several seconds as the case may be) before it snaps into focus? Maybe it's the queue again. But it does this even if the preview hasn't been updated, and you're just flipping through a couple of frames.

I've never seen any noticeable slider delay. That part is fine. But going through a large shoot can be a serious test of patience.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 28, 2017 2
Explorer ,
Apr 29, 2017

Copy link to clipboard

Copied

well, this didn't last long.

Just finished a job. imported 1300 new images. And LR is bag to it's useless slowness. culling these images will take a while ...

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 29, 2017 1
Explorer ,
May 03, 2017

Copy link to clipboard

Copied

Ok. Looks like I have found the issue. After I reinstalled the driver, I also re calibrated the monitor using the spyder pro. And after I did that, LR started lagging again. So I deleted the monitor profile made by spyder. And then LR worked as normal.

This isn't a good solution. Any idea why that happens?

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
May 03, 2017 0
Adobe Community Professional ,
May 03, 2017

Copy link to clipboard

Copied

That's interesting, and it has been discussed before. The thing is that the monitor profile is constantly read, and every time you make an adjustment, a new conversion is performed.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
May 03, 2017 0
Adobe Community Professional ,
May 03, 2017

Copy link to clipboard

Copied

Yep, it's been discussed way to many times with no assistance coming form Adobe Staff. LR is very finicky about the type of display profile and some may work fine with PS, but cause performance or rendering issues (color, contrast) with LR.

The general consensus is that a Matrix ICC Version 2 profile is most compatible, and Lookup Table (LUT) ICC Version 4 profiles may cause issues. I say "may" because some users have reported no issues with either profile type. What Spyder model are you using? Try creating a new Spyder profile using the 'Expert' or 'Advanced' mode and selecting 'Matrix for profile type and ICC Version 2. The availability of these settings varies by Spyder model and perhaps even generation (3, 4, 5).

Please let us know your results and I will try to get this resolved.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
May 03, 2017 0
Adobe Community Professional ,
May 03, 2017

Copy link to clipboard

Copied

The general consensus is that a Matrix ICC Version 2 profile is most compatible, and Lookup Table (LUT) ICC Version 4 profiles may cause issues.

True, and it's perfectly possible the Spyder makes v4 by default. LUT is less likely, it's probably just matrix.

However, in this case I was more thinking along the lines of "profile drag" so to speak, a profile that basically works, but has some problems that cause the app to slow down. I remember someone (Rob Cole?) digging into things and being genuinely surprised at how much time and CPU cycles were spent on loading and reading the monitor profile.

I use ColorNavigator, which has a lot of options for profile policies and general anatomy. It also lets you quickly switch between profiles (although an app relaunch is still required). In any case, I'll keep an eye on this.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
May 03, 2017 0
Adobe Employee ,
May 03, 2017

Copy link to clipboard

Copied

Which version of the Spyder device?

What is your software version currently in use from Datacolor?

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
May 03, 2017 0
Adobe Employee ,
May 03, 2017

Copy link to clipboard

Copied

Additionally, is there any chance you saved that problematic profile and would be willing to share it with us?

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
May 03, 2017 0
Explorer ,
May 11, 2017

Copy link to clipboard

Copied

deleted the profile.

used spyder 5 pro

latest software

3440x1440.

I have a dual monitor setup.

Can't say I notice any difference with GPU acc on or off. except from when doing GPU heavy tasks like transform.

note, I am not using any additional color profile. But the lag is back. killing me slowly.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
May 11, 2017 0
Adobe Community Professional ,
May 11, 2017

Copy link to clipboard

Copied

Tiboine  wrote

deleted the profile.

used spyder 5 pro

latest software

3440x1440.

I have a dual monitor setup.

Did you use the Advanced or Expert mode that let's you select ICC Version 2 and Matrix type profile? Are you calibrating both displays. What resolution is the 2nd display?

Tiboine  wrote

Can't say I notice any difference with GPU acc on or off. except from when doing GPU heavy tasks like transform.

Are you using LR with dual monitors? There is currently no GPU support for the Secondary display. If using a 3440x1440 monitor for the Secondary Loupe display it will be dog slow!

Regardless if you're using dual-displays with LR or NOT–How does LR behave if you shutdown, disconnect the 2nd display, and reboot?

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
May 11, 2017 0
Explorer ,
Sep 03, 2017

Copy link to clipboard

Copied

no such options available in spyder as far as I can see.  second display is 1920x1200. I don't use it for LR.

no change when disconnecting the monitor.

any word on the next LR update?

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Sep 03, 2017 0
Participant ,
Sep 24, 2017

Copy link to clipboard

Copied

LR on iPad Pro is faster than my 5k working station.....

Thank you marketing guys.. we don't work all the time on remote location...

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Sep 24, 2017 0
Adobe Employee ,
May 04, 2017

Copy link to clipboard

Copied

What is the resolution of the monitor? Do you have dual monitor setup? GPU acceleration on and working?

The type of color profile might be a factor.

There is a bug fix a while back in the context of soft-proofing where Lr would scan the color profiles more often than necessary. But in general, Lr would read the monitor color profile once per application session, reuse the cached version when requested later.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
May 04, 2017 0
Community Beginner ,
May 08, 2017

Copy link to clipboard

Copied

Simonsaith, would you mind reading my post above and see what you think?  I do not get the black screen Tiboine is getting, but I do get a flash of a crash screen if I sometimes do something as simple as changing exposure.  I definitely get the lags of trying to focus the image on 1x1.  It also lags so much just trying to update any change on a new image.  I've tried everything to speed up the process.  It's driving me crazy.  I wonder if MAC users have these issues?  Thanks in advance.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
May 08, 2017 0
Participant ,
May 29, 2017

Copy link to clipboard

Copied

Hi there,

I've got the same problem... Hi end PC working station for video editing.

Since I've got my sony alpha 7rii, now my DNG fils are more than 20 mo, when it was 4 mo evrything was fast and smooth...

Can may be the dev team can work on multi cpu used with Lightroom. We all feel that the code/software is for dslr more than 2/3 years...

This can't go like this for ever...

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
May 29, 2017 0
Explorer ,
Nov 27, 2017

Copy link to clipboard

Copied

After the Classic "update", LR is still slow as poop. can take upto 5 seconds to mark a few images in grid.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Nov 27, 2017 0
New Here ,
Nov 03, 2019

Copy link to clipboard

Copied

I know this is an old thread and I was doing research as I was also finding slowness and was in search of a solution... This thread was helpful and it also made me thing of trying another parameter... Windows Power Plan... as I noticed when benchmarking and measuring power comsumption there is a big difference... If you use High performance or Ultimate Performance... LR will hum along nicely. but in Power Saver plan CPU and GPU are clock limited and you will have terrible performance.  This might be why when you initially reinstalled the driver (removing an power plan settings) it was good and then after some time or updates those setting could have been reinserted in (see the Advanced setting for power plans to see what is being changed in each plan...) here is an App I use to quickly switch power plans   

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Nov 03, 2019 0
Community Beginner ,
Jan 24, 2020

Copy link to clipboard

Copied

I know this is a really old thread but I'm in a similar situation. 
I'mrunning an

Asus extreme Maximus iii motherboard

i76700k skylake

32 gb of 3200 megahertz Corsair RGB ram 

radeon 7 gpu

m.2 ssd 970 pro evo 1tb Samsung 

in a case with proper airflow. 
I know my cpu is a bit dated but I was having no issues what so ever before. 
For the last few years I have ran a hackinsosh build with this very system with high Sierra and Mojave. With little to no issues with premier pro and Lightroom. 
I ran this system with another normal sata ssd to run windows for gaming and such 

as of late I wanted to fully switch over to windows  so did a clean install on the m.2 1tb drive and did some test edits with a folder of 4 raw images from my Sony a7iii everything ran pretty fine as far as normal develop stuff but any cropping or rotating it lags like crazy. I never had this issue with my Mac side ever. Switching from photo to photo seems to be quite slower too. I have tried every normal thing that's recommended on here.  Even did another clean install of windows 

My gpu is updated to the latest drivers. 
I tried new ram

tried a different m.2 ssd 

changed my cache size to 50 gb 

tured on and off gpu acceleration with little to no effect. 
Using standard color profile 

I have plenty or storage on the c drive and that's where the catalog is and the raw images are on there too. 

All changing nothing. Same consistent lag across the board. 
Plus premier pro is making me render 1080p footage every time I do so much as add a cross fade or extend a clip. At a 1/4th preview 

never had this issue on my Mac side. 
I pay over 50 bucks a month for these programs 

the hardware I'm using is more than adequate to to run edit 24 megapixel raw images & edit 1080p footage in a single clip timeline. 
come on adobe. Just because you have pretty much a Monopoly on the market at the moment doesn't mean you should slack off this much. 
I'm about fed up and thinking of switching to da Vinci resolve and capture one. 

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jan 24, 2020 0
New Here ,
Mar 28, 2020

Copy link to clipboard

Copied

I'm convinced Adobe just doesn't care anymore.  We are running LR classic on a Windows 10 PC with a Ryzen 3600X overclocked with 32 GB of fast RAM, an AMD Radeon Vega 64 (overclocked and undervolted), and only fast SSDs with the OS on a M.2 NVME SSD.  STILL LR Classic is slow to switch between modules, slow to open, slow to develop, etc.  Windows 10 Home version 10.0.18362 Build 18362 and the most up to date driver for the Vega 64.  GET IT TOGETHER ADOBE!

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Mar 28, 2020 0
New Here ,
Jun 21, 2020

Copy link to clipboard

Copied

Adobe is the worst company I have ever worked with.  Broken software even with excellent hardware.  

 

Lightroom Classic version: 9.3 [ 202005281810-476e492c ]
License: Creative Cloud
Language setting: en
Operating system: Windows 10 - Home Premium Edition
Version: 10.0.18362
Application architecture: x64
System architecture: x64
Logical processor count: 12
Processor speed: 4.1 GHz
SqLite Version: 3.30.1
Built-in memory: 32701.3 MB
Real memory available to Lightroom: 32701.3 MB
Real memory used by Lightroom: 5370.8 MB (16.4%)
Virtual memory used by Lightroom: 23673.7 MB
GDI objects count: 1647
USER objects count: 2862
Process handles count: 4450
Memory cache size: 500.0MB
Internal Camera Raw version: 12.3 [ 493 ]
Maximum thread count used by Camera Raw: 5
Camera Raw SIMD optimization: SSE2,AVX,AVX2
Camera Raw virtual memory: 3420MB / 16350MB (20%)
Camera Raw real memory: 2809MB / 32701MB (8%)
System DPI setting: 96 DPI
Desktop composition enabled: Yes
Displays: 1) 1920x1200
Input types: Multitouch: Yes, Integrated touch: Yes, Integrated pen: No, External touch: No, External pen: No, Keyboard: No

Graphics Processor Info:
DirectX: Radeon RX Vega (26.20.15029.27016)



Application folder: C:\Program Files\Adobe\Adobe Lightroom Classic
Library Path: D:\Crystal Lightroom\Crystals Lightroom Catalog\Crystal's Lightroom Catalog\Crystal's Lightroom Catalog-2.lrcat
Settings Folder: C:\Users\dustinkeffer\AppData\Roaming\Adobe\Lightroom

Installed Plugins:
1) PugetBench for Lightroom Classic

Config.lua flags: None

Adapter #1: Vendor : 1002
Device : 687f
Subsystem : b361002
Revision : c1
Video Memory : 8119
Adapter #2: Vendor : 1414
Device : 8c
Subsystem : 0
Revision : 0
Video Memory : 0
AudioDeviceIOBlockSize: 1024
AudioDeviceName: 1 - DELL U2415 (AMD High Definition Audio Device)
AudioDeviceNumberOfChannels: 2
AudioDeviceSampleRate: 48000
Build: LR5x42
Direct2DEnabled: false
GL_ACCUM_ALPHA_BITS: 0
GL_ACCUM_BLUE_BITS: 0
GL_ACCUM_GREEN_BITS: 0
GL_ACCUM_RED_BITS: 0
GL_ALPHA_BITS: 8
GL_BLUE_BITS: 8
GL_DEPTH_BITS: 24
GL_GREEN_BITS: 8
GL_MAX_3D_TEXTURE_SIZE: 2048
GL_MAX_TEXTURE_SIZE: 16384
GL_MAX_TEXTURE_UNITS: 8
GL_MAX_VIEWPORT_DIMS: 16384,16384
GL_RED_BITS: 8
GL_RENDERER: Radeon RX Vega
GL_SHADING_LANGUAGE_VERSION: 4.60
GL_STENCIL_BITS: 8
GL_VENDOR: ATI Technologies Inc.
GL_VERSION: 4.6.13587 Compatibility Profile Context 20.4.2 26.20.15029.27016
GPUDeviceEnabled: false
OGLEnabled: true
GL_EXTENSIONS: GL_AMDX_debug_output GL_AMD_blend_minmax_factor GL_AMD_conservative_depth GL_AMD_debug_output GL_AMD_depth_clamp_separate GL_AMD_draw_buffers_blend GL_AMD_framebuffer_sample_positions GL_AMD_gcn_shader GL_AMD_gpu_shader_half_float GL_AMD_gpu_shader_half_float_fetch GL_AMD_gpu_shader_int16 GL_AMD_gpu_shader_int64 GL_AMD_interleaved_elements GL_AMD_multi_draw_indirect GL_AMD_name_gen_delete GL_AMD_occlusion_query_event GL_AMD_performance_monitor GL_AMD_pinned_memory GL_AMD_query_buffer_object GL_AMD_sample_positions GL_AMD_seamless_cubemap_per_texture GL_AMD_shader_atomic_counter_ops GL_AMD_shader_stencil_export GL_AMD_shader_stencil_value_export GL_AMD_shader_trace GL_AMD_shader_trinary_minmax GL_AMD_sparse_texture GL_AMD_sparse_texture_pool GL_AMD_stencil_operation_extended GL_AMD_texture_cube_map_array GL_AMD_texture_texture4 GL_AMD_transform_feedback3_lines_triangles GL_AMD_transform_feedback4 GL_AMD_vertex_shader_layer GL_AMD_vertex_shader_viewport_index GL_ARB_ES2_compatibility GL_ARB_ES3_1_compatibility GL_ARB_ES3_compatibility GL_ARB_arrays_of_arrays GL_ARB_base_instance GL_ARB_bindless_texture GL_ARB_blend_func_extended GL_ARB_buffer_storage GL_ARB_clear_buffer_object GL_ARB_clear_texture GL_ARB_clip_control GL_ARB_color_buffer_float GL_ARB_compatibility GL_ARB_compressed_texture_pixel_storage GL_ARB_compute_shader GL_ARB_conditional_render_inverted GL_ARB_conservative_depth GL_ARB_copy_buffer GL_ARB_copy_image GL_ARB_cull_distance GL_ARB_debug_output GL_ARB_depth_buffer_float GL_ARB_depth_clamp GL_ARB_depth_texture GL_ARB_derivative_control GL_ARB_direct_state_access GL_ARB_draw_buffers GL_ARB_draw_buffers_blend GL_ARB_draw_elements_base_vertex GL_ARB_draw_indirect GL_ARB_draw_instanced GL_ARB_enhanced_layouts GL_ARB_explicit_attrib_location GL_ARB_explicit_uniform_location GL_ARB_fragment_coord_conventions GL_ARB_fragment_layer_viewport GL_ARB_fragment_program GL_ARB_fragment_program_shadow GL_ARB_fragment_shader GL_ARB_framebuffer_no_attachments GL_ARB_framebuffer_object GL_ARB_framebuffer_sRGB GL_ARB_geometry_shader4 GL_ARB_get_program_binary GL_ARB_get_texture_sub_image GL_ARB_gl_spirv GL_ARB_gpu_shader5 GL_ARB_gpu_shader_fp64 GL_ARB_half_float_pixel GL_ARB_half_float_vertex GL_ARB_imaging GL_ARB_indirect_parameters GL_ARB_instanced_arrays GL_ARB_internalformat_query GL_ARB_internalformat_query2 GL_ARB_invalidate_subdata GL_ARB_map_buffer_alignment GL_ARB_map_buffer_range GL_ARB_multi_bind GL_ARB_multi_draw_indirect GL_ARB_multisample GL_ARB_multitexture GL_ARB_occlusion_query GL_ARB_occlusion_query2 GL_ARB_parallel_shader_compile GL_ARB_pipeline_statistics_query GL_ARB_pixel_buffer_object GL_ARB_point_parameters GL_ARB_point_sprite GL_ARB_polygon_offset_clamp GL_ARB_program_interface_query GL_ARB_provoking_vertex GL_ARB_query_buffer_object GL_ARB_robust_buffer_access_behavior GL_ARB_sample_shading GL_ARB_sampler_objects GL_ARB_seamless_cube_map GL_ARB_seamless_cubemap_per_texture GL_ARB_separate_shader_objects GL_ARB_shader_atomic_counters GL_ARB_shader_ballot GL_ARB_shader_bit_encoding GL_ARB_shader_draw_parameters GL_ARB_shader_group_vote GL_ARB_shader_image_load_store GL_ARB_shader_image_size GL_ARB_shader_objects GL_ARB_shader_precision GL_ARB_shader_stencil_export GL_ARB_shader_storage_buffer_object GL_ARB_shader_subroutine GL_ARB_shader_texture_image_samples GL_ARB_shader_texture_lod GL_ARB_shader_viewport_layer_array GL_ARB_shading_language_100 GL_ARB_shading_language_420pack GL_ARB_shading_language_packing GL_ARB_shadow GL_ARB_shadow_ambient GL_ARB_sparse_buffer GL_ARB_sparse_texture GL_ARB_spirv_extensions GL_ARB_stencil_texturing GL_ARB_sync GL_ARB_tessellation_shader GL_ARB_texture_barrier GL_ARB_texture_border_clamp GL_ARB_texture_buffer_object GL_ARB_texture_buffer_object_rgb32 GL_ARB_texture_buffer_range GL_ARB_texture_compression GL_ARB_texture_compression_bptc GL_ARB_texture_compression_rgtc GL_ARB_texture_cube_map GL_ARB_texture_cube_map_array GL_ARB_texture_env_add GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_ARB_texture_float GL_ARB_texture_gather GL_ARB_texture_mirror_clamp_to_edge GL_ARB_texture_mirrored_repeat GL_ARB_texture_multisample GL_ARB_texture_non_power_of_two GL_ARB_texture_query_levels GL_ARB_texture_query_lod GL_ARB_texture_rectangle GL_ARB_texture_rg GL_ARB_texture_rgb10_a2ui GL_ARB_texture_snorm GL_ARB_texture_stencil8 GL_ARB_texture_storage GL_ARB_texture_storage_multisample GL_ARB_texture_swizzle GL_ARB_texture_view GL_ARB_timer_query GL_ARB_transform_feedback2 GL_ARB_transform_feedback3 GL_ARB_transform_feedback_instanced GL_ARB_transform_feedback_overflow_query GL_ARB_transpose_matrix GL_ARB_uniform_buffer_object GL_ARB_vertex_array_bgra GL_ARB_vertex_array_object GL_ARB_vertex_attrib_64bit GL_ARB_vertex_attrib_binding GL_ARB_vertex_buffer_object GL_ARB_vertex_program GL_ARB_vertex_shader GL_ARB_vertex_type_10f_11f_11f_rev GL_ARB_vertex_type_2_10_10_10_rev GL_ARB_viewport_array GL_ARB_window_pos GL_ATI_draw_buffers GL_ATI_envmap_bumpmap GL_ATI_fragment_shader GL_ATI_separate_stencil GL_ATI_texture_compression_3dc GL_ATI_texture_env_combine3 GL_ATI_texture_float GL_ATI_texture_mirror_once GL_EXT_abgr GL_EXT_bgra GL_EXT_bindable_uniform GL_EXT_blend_color GL_EXT_blend_equation_separate GL_EXT_blend_func_separate GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_compiled_vertex_array GL_EXT_copy_buffer GL_EXT_copy_texture GL_EXT_depth_bounds_test GL_EXT_direct_state_access GL_EXT_draw_buffers2 GL_EXT_draw_instanced GL_EXT_draw_range_elements GL_EXT_fog_coord GL_EXT_framebuffer_blit GL_EXT_framebuffer_multisample GL_EXT_framebuffer_object GL_EXT_framebuffer_sRGB GL_EXT_geometry_shader4 GL_EXT_gpu_program_parameters GL_EXT_gpu_shader4 GL_EXT_histogram GL_EXT_memory_object GL_EXT_memory_object_win32 GL_EXT_multi_draw_arrays GL_EXT_packed_depth_stencil GL_EXT_packed_float GL_EXT_packed_pixels GL_EXT_pixel_buffer_object GL_EXT_point_parameters GL_EXT_polygon_offset_clamp GL_EXT_provoking_vertex GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_semaphore GL_EXT_semaphore_win32 GL_EXT_separate_specular_color GL_EXT_shader_image_load_store GL_EXT_shader_integer_mix GL_EXT_shadow_funcs GL_EXT_stencil_wrap GL_EXT_subtexture GL_EXT_texgen_reflection GL_EXT_texture3D GL_EXT_texture_array GL_EXT_texture_buffer_object GL_EXT_texture_compression_bptc GL_EXT_texture_compression_latc GL_EXT_texture_compression_rgtc GL_EXT_texture_compression_s3tc GL_EXT_texture_cube_map GL_EXT_texture_edge_clamp GL_EXT_texture_env_add GL_EXT_texture_env_combine GL_EXT_texture_env_dot3 GL_EXT_texture_filter_anisotropic GL_EXT_texture_integer GL_EXT_texture_lod GL_EXT_texture_lod_bias GL_EXT_texture_mirror_clamp GL_EXT_texture_object GL_EXT_texture_rectangle GL_EXT_texture_sRGB GL_EXT_texture_sRGB_R8 GL_EXT_texture_sRGB_RG8 GL_EXT_texture_sRGB_decode GL_EXT_texture_shared_exponent GL_EXT_texture_snorm GL_EXT_texture_storage GL_EXT_texture_swizzle GL_EXT_timer_query GL_EXT_transform_feedback GL_EXT_vertex_array GL_EXT_vertex_array_bgra GL_EXT_vertex_attrib_64bit GL_IBM_texture_mirrored_repeat GL_INTEL_fragment_shader_ordering GL_KHR_context_flush_control GL_KHR_debug GL_KHR_no_error GL_KHR_parallel_shader_compile GL_KHR_robust_buffer_access_behavior GL_KHR_robustness GL_KTX_buffer_region GL_NV_alpha_to_coverage_dither_control GL_NV_blend_square GL_NV_conditional_render GL_NV_copy_depth_to_color GL_NV_copy_image GL_NV_depth_buffer_float GL_NV_explicit_multisample GL_NV_float_buffer GL_NV_half_float GL_NV_primitive_restart GL_NV_shader_atomic_int64 GL_NV_texgen_reflection GL_NV_texture_barrier GL_OES_EGL_image GL_SGIS_generate_mipmap GL_SGIS_texture_edge_clamp GL_SGIS_texture_lod GL_SUN_multi_draw_arrays GL_WIN_swap_hint WGL_EXT_swap_control

Passmark benchmark 6.2020.PNG

Despite all this the develop module frequently freezes, it takes forever to navigate the library and switch modules.  TERRIBLE.  

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jun 21, 2020 0