Lightroom 2015.6 Extremely Slow

  • 43
  • Problem
  • Updated 1 year ago

I am not sure if this is the best place to post this but I am extremely frustrated! This version is extremely slower than the previous version, which in turn was slower than the one before it. Moving from one image to the next, takes at least 5seconds and adjusting any slider causes Lightroom to freeze, with the lovely "circle of death" reminding me that it's thinking and I should not perform any actions, for 2 seconds or so. I am a very tolerant person but feel like I've had it now! It feels like I am falling out of love with a craft that I once was excited about because editing, which is a very important part of the process, doesn't work. And instead of improving, Lightroom has quickly gotten worse over time! It has taken me 2 and a half days to edit 450 photos, and there's a few more to do but Lightroom has now CRASHED hence my angst here! I have a couple jobs more to edit and I am in a position where I am not seeking after more work because of a backlog of jobs to edit. This is really costing me and I am very angry because I just want to get on with my work. Yes I have a decent system, yes I have plenty of RAM, yes I have a SSD installed. ADOBE, please please please, I just want to edit and enjoy it.

Photo of Jerry Syder

Jerry Syder

  • 181 Posts
  • 88 Reply Likes

Posted 2 years ago

  • 43
Photo of Stefan Redel

Stefan Redel

  • 87 Posts
  • 29 Reply Likes
Same to me. OK, not that worse, but it feels way slower than previous version or even 2015.1 or .2.
Photo of Diko

Diko

  • 77 Posts
  • 9 Reply Likes
The crash is maybe because of a memory leak (I think) I observed. Need more data to collect and send them. As for the rest, I am just like you. :-(
Photo of Jerry Syder

Jerry Syder

  • 181 Posts
  • 88 Reply Likes
I rarely post problems because I always think someone would have already posted about my issue. I just couldn't help myself here. It's that bad! The numbers and stats I've listed are precise btw!! Man, I hope they look into it.. I'm pulling my locks out here ha!
Photo of Gwen Hornsby

Gwen Hornsby

  • 1 Post
  • 0 Reply Likes
I agree this is really driving me crazy - Lightroom keeps stopping everytime I move a slider or switch to a new image.  My work is getting further behind and I have about 30 shoots to finish - arggggggg - Come one Adobe give us back the previous version at least it didn't keep stopping.
Photo of Stefan Redel

Stefan Redel

  • 87 Posts
  • 29 Reply Likes
Gwen, then do this. It takes you 10 minutes and after that you're much happier:

https://helpx.adobe.com/lightroom/kb/roll-back-to-prior-update.html
Photo of Mihael Tominšek

Mihael Tominšek

  • 37 Posts
  • 31 Reply Likes
U're not alone. Lr is slower and slower. On my 6-core/32GB/3x ssd computer Lr is always slow. 
One option you have is to DISABLE "lens correction" and "detail" panel. Especially later, because noise reduction, which Lr calculates at every "develop slider" change, really slows things down. 

But it is upside down worklflow and U must turn it image per image (times 450 images), and later again switch panels on, image per image (times 450). 

It definitely helps, but it is another pain to do it. 

Adobe should (no, Adobe MUST) provide global turn on/off of panels. Several smart(er) software (or Premiere plugins) have this function built in, so U can disable rendering effect until restart/or export. 

Hope it helps. 
(Edited)
Photo of Jerry Syder

Jerry Syder

  • 179 Posts
  • 88 Reply Likes
I will try that Mihael, - turn it off image by image? Wow! Umm I will try that but Adobe should really sort this. Thanks for your reply
Photo of Diko

Diko

  • 77 Posts
  • 9 Reply Likes
I say OK. And yet total nonsense. To turn off features in order to kick the old bucket running!?!
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 3774 Posts
  • 1249 Reply Likes
That shouldn't be necessary. Adobe would much rather figure out why it's that slow for you and not for most users. The more information you can provide on system specs, monitor resolution and graphics card (& its driver version), camera type, timings, etc, the more likely they are to find the pattern.
Photo of Mihael Tominsek

Mihael Tominsek

  • 52 Posts
  • 19 Reply Likes
I appreciate Victoria, if Adobe would fix this. But I do not know user that would say Lr is fast. I tried C1 - it have a lot of shortcoming too, but it is not as stammeing as Lr when loading image ir moving sliders. I use Lr from Version 1,5... never was fast. As computers goes faster, images grow in size, so relatively we are the same after decades. And I have everything on SSD's, separate for system, Lr catalog and cache (12GB), and images, than GTX770 card, 32GB 2133 ram, 6-core cpu... and I wait for sliders... not (so much) if I disable NR and sharpening and lens distortion. But still... I remember now defunct CINEFORM FIRST LIGHT software - RT as it can be - for video. Yes we like Adobe integration, but we pay it hard every day. I must say that I search elsewhere for alternative. But Adobe won this buying all relevant products in the past. 
(Edited)
Photo of Mihael Tominšek

Mihael Tominšek

  • 37 Posts
  • 31 Reply Likes
I have 99 GB of cache now. Maybe it is slightly more fluent..
Photo of Mihael Tominšek

Mihael Tominšek

  • 37 Posts
  • 31 Reply Likes
... some say you enlarge Lightroom CACHE to some odd large figure, like 20GB... I did it to 13 GB (as my space allows), but I cant swear by it helps much. Disabling panels, does. 
(Edited)
Photo of Stefan Redel

Stefan Redel

  • 87 Posts
  • 29 Reply Likes
That doesn't help. LR CC 2015.6 is slower than 2015.5.1.

(Cache is 50 GB here, always a new catalog for each project. Everything is most possible optimized. Logically the solution can't be to optimize here and there (noisereduction off, etc), because it worked better before 2015.6.)
Photo of Jerry Syder

Jerry Syder

  • 179 Posts
  • 88 Reply Likes
Agree on this, mine is even larger(90GB) and I've never seen an improvement. I'm also optimised out!
Photo of Diko

Diko

  • 77 Posts
  • 9 Reply Likes
So is mine. (88 GB).

Nothing.

Build 1:1, running both catalog and DNG files doesn't improves local adjustment and spot removal at all. Neither is my video card which btw is almost unused the whole time. :-(
(Edited)
Photo of Stefan Redel

Stefan Redel

  • 87 Posts
  • 29 Reply Likes
Hups, please try this:
Stop LR, Start LR, be happy with the speed. :)

OK... Why i'm telling that: Had a Baby here two hours ago and made the preview for the clients. It took me 30 minutes (!) for just 220 pictures from Canon 5D3 for the 1:1-Preview. Switching from one picture to another was a pain in the a.... So unbelievable slow. Note: Nothing has changed since generation of the preview, the Cache is 50 Gig, RAM is 32 Gig, newest Intel 8-Core at 4GHz. Slower than usual.
Than i stopped LR, did something else, started LR with another catalogue and it is fast! Hmmm...
Normally i'm browsing through the pictures right after having done the Preview. And that was fast. OK, somewhat fast. Now it's annoying slow.
Maybe we have to restart LR after generating the Cat and the Preview?
Photo of Stefan Redel

Stefan Redel

  • 87 Posts
  • 29 Reply Likes
Addition: RAM-Usage was around 15 Gigs for all while it was unbelievable slow.
Now RAM-Usage overall (for the System) is something around 6 to 9 Gigs. Hmmm...
Photo of Stefan Redel

Stefan Redel

  • 87 Posts
  • 29 Reply Likes
2nd Addition.
RAM-Usage goes up again to 15 Gigs and LR slows down. But not that dramatic way.
Minimizing (not closing) LR and the Usage goes down to 7 to 8 Gigs.
Maximing LR and it runs again fast.
Memory Leak?
Photo of Mihael Tominšek

Mihael Tominšek

  • 37 Posts
  • 31 Reply Likes
Yes after time of usage Lr become "clogged" up and restart helps wastly. But that was with small cache. In 99 GB of cache that is not the case any moore. But unfortunatelky we are talking of it's natural slowness, not extra slowness when cache is full. 
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 3170 Posts
  • 516 Reply Likes
Jerry,

I would recommend the following:

1. Reset your preferences file by closing Lightroom, holding down [Alt/Opt]+[Shift] and relaunching Lightroom. Overwrite the preference file when requested. 
2. After preference reset, uninstall Lightroom from the Creative Cloud App.
3. Reboot.
4. Install Lightroom via the Creative Cloud App. 
5. After installation, Optimize the catalog first thing. 

Does you performance/stability improve now?
Photo of Assaf Frank

Assaf Frank

  • 147 Posts
  • 44 Reply Likes
can't be certain that I can see improvement, but thank you for the tip.

the plugins - if there were located in the modules folder
C:\Users\User\AppData\Roaming\Adobe\Lightroom\Modules
they lasted the reset other wise the didn't so I have moved them to that folder and they came back.

important point about spot removal which is an issue with the last version as well.
1. I'm aware of the GPU acceleration issue - that it works faster without it.
2. I found that the main problem of slowness by far is the 4K resolution
3. for example if I do spot removal on 4k on big panoramas of 40000x7000 pixels (280MP) it takes about 8 seconds between each spot removal click to until I get my mouse control back (this includes black screen flicking back and forth). GPU acceleration off., with GPU Acceleration on its about 13 seconds for each spot removal click, and the detail tab is switched off (noise removal).
4. now the best part is that once I switch to 1920x1080 it is instant yes !! on the same massive file.
5. my spec is Nvida GTX 980 Ti, i7 5960X 8 core 64GB DDR4 everything is on m.2 PCI EXpress NVME and SSDs 
6. my files are Phase one IQ280 - 80MP
7. The slowness is in everything but mostly in spot or local adjustments functions (with the GPU off) the when I do sliders adjustment WB / Exposure I turn the GPU back on and its relatively ok in 4K but in 1920x1080 its super fast.

I have the latest drives from nvidia.

any suggestion will be welcomed.
(Edited)
Photo of Gary Kramer

Gary Kramer

  • 1 Post
  • 1 Reply Like
This corrected the issues I have been having since the most recent update. Thank you.
Photo of Kostadin Luchansky

Kostadin Luchansky

  • 22 Posts
  • 5 Reply Likes
Hi @Rikk,
If we do this procedure (uninstalling and reinstalling Lightroom CC 2016), will we loose any personalised settings and configurations?
I'm willing to try.
Thanks,
Kostadin
(Edited)
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 3170 Posts
  • 516 Reply Likes
A backup is always prudent.

Your catalog and user-defined settings should remain intact. 
Photo of Assaf Frank

Assaf Frank

  • 147 Posts
  • 44 Reply Likes
I presume I will need to reinstall all the plugins?
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 3170 Posts
  • 516 Reply Likes
Normally, no. They should come along for the ride. 
Photo of Trevor Morris

Trevor Morris

  • 20 Posts
  • 7 Reply Likes
After using this version for a couple days now, I’m finding it significantly slower (painfully so) than the previous version. Turning off “Use Graphics Processor” seems to help. As soon as I have some time, I'll also try the advice provided above.
Photo of Assaf Frank

Assaf Frank

  • 147 Posts
  • 44 Reply Likes
4k display?
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 3831 Posts
  • 1269 Reply Likes
Those of you who are seeing new performance issues in 6.6, can you keep your eye on Activity Monitor and see what the RAM usage is like when it's going slowly? I've seen it ramp up the RAM use to crazy levels twice, but I haven't managed to figure out how to trigger it yet.
Photo of Mike Engles

Mike Engles

  • 26 Posts
  • 2 Reply Likes

Hello jeckylproductions

You still have not said what size previews you are using. It might be very important to give Adobe a clue. Have you tried much smaller previews like 1440, just as a test. Make a test folder with 50 images and try smaller previews till you get an acceptable performance.

There is obviously something seriously wrong with how Lightroom works on some computers.

MDE

(Edited)
Photo of jeckylproductions

jeckylproductions

  • 8 Posts
  • 3 Reply Likes
Hey Mike, thanks for asking, I mentioned I was rendering them at 2048 in another area of this thread but forgot to here.  Regardless of rendering 1:1 previews, even when it is not rendering previews it is leaking memory.  I can remain on one image and move my mouse across the image and watch in the resource monitor the memory use increase, this does not change unless I close or minimize LR.

I'd say forget about the 1:1 rendering as an issue, I think as a whole their is an issue with memory, cpu and GFX card usage in this version.  Their is a problem with the build overall, I thought I waited long enough before installing 2015.6 and it's release, obviously not.

I'd just prefer to rollback if someone has a walk though or link for that?
Photo of Mike Engles

Mike Engles

  • 26 Posts
  • 2 Reply Likes

Hello

Thanks for the reply.

2048 is not very large for a preview, I use 1920x1200.

I don't generally use GPU. In my system the GPU makes panning at 1:1 quite smooth, but the actual redraw is slower. Also all the sliders are really notchy and results in an overshoot.

Without GPU panning can be smooth, but mostly very notchy and clicking on another image can take quite a long time to change whilst panning. The sliders are smooth and there is no overshoot. This pretty well the same behaviour for all the versions of Lightroom 6, but 6.6 is slightly worse.

I don't have CC so I can just go to the Adobe site and download older versions. I have not gone back to 5.7, even though I have it. The GPU would not work with 5.7

https://helpx.adobe.com/lightroom/kb/lightroom-downloads.html

This links to previous versions of Lightroom

MDE





Photo of Mike Engles

Mike Engles

  • 26 Posts
  • 2 Reply Likes

Hello

I have started this topic, you might be interested in

https://feedback.photoshop.com/photoshop_family/topics/why-does-lightroom-use-so-many-resources/edit

There seems to be a lot of problems concerning the performance of Lightroom 6.6

At the moment I am on Lightroom 6.5 standalone.

I use Win 7 pro on a 6 year old i7 870 Quadcore with 16gb of ram, a Samsung SSD and a AMD 5450 video card

I have just done a small experiment.

With just Windows running the resource monitor shows that the ram in use is 2354mb

I created a new catalogue on the SSD. Cache 100gb, video cache 10gb

The ram in use went to 2633mb

I added one Canon 5D3 image to the catalogue and created a 1920x1200 preview with high

quality.

The ram in use with no edits went to 3585mb

Now the 1920x1200 preview at 16bit should be about 13mb

So why has the addition of just one image to the catalogue increased ram usage by 952mb

Using Develop and no edits I zoomed 100% and panned the image about.

This was smooth, but the ram usage went to 4371mb, an increase of another 786mb.

This one image takes up 1738mb

Now I did some edits in exposure, clarity, vibrance, lens profile and auto upright, zoom to 100% and panned again.

Ram use went to 4606mb, up another 235mb.

That is a total of nearly 2000mb for one 13mb image.

Now I added 7 100,75,100 clones, zoomed 1:1 and repeated the panning.

No GPU the panning was very smooth and redraw was pretty instant and no CPU thrashing, which happens in my normal catalogue.  

Ram uses goes up to 4919mb

That is with cloning and the above processing, ram use for one 13mb image is 2286mb.

This the memory usage in Sys info

Built-in memory: 16374.1 MB
Real memory available to Lightroom: 16374.1 MB
Real memory used by Lightroom: 1902.2 MB (11.6%)
Virtual memory used by Lightroom: 1947.2 MB
Memory cache size: 276.3 MB

Quite amazing.

MDE

Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1385 Posts
  • 413 Reply Likes
Depends on your RAM availability, Lightroom caches a few of the last loaded negatives in the RAM just in case you might do something with it (develop it or walking back and forth between two photos etc) in the next moment. Lightroom wants to keep it available just in case. It is not he JPEG previews that took up the RAM.
(Edited)
Photo of David Efurd

David Efurd

  • 13 Posts
  • 5 Reply Likes
I'm pretty much in the same boat as the OP. Latest LR update has made it pretty much unusable. For me, it's CPU not Memory. My CPU gets pegged any time I try to make any adjustments in develop module. A simple adjustment of say highlights causes the CPU to spike and it takes 3-4 seconds to recover and be able to do anything else again. Just switching from develop to library module takes 5+ seconds. It's very frustrating and making me seriously consider trying out Capture One Pro since I can't afford to be impacted like this with one of the major tools of my workflow. Didn't have any of these issues prior to the update a few days ago.
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 3774 Posts
  • 1249 Reply Likes
Oh, and also check whether the GPU is enabled in Preferences or not.
Photo of David Efurd

David Efurd

  • 13 Posts
  • 5 Reply Likes
Thanks for the suggestions. GPU is definitely enabled. I've heard some folks recommending to turn that off but that's supposed to be a good thing to offload work from the CPU to a GPU, no?  Not sure what you mean by sync - is that syncing between desktop and mobile? I've never used that and have never even logged into LR mobile before.
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 3774 Posts
  • 1249 Reply Likes
Correct, GPU is most useful on high resolution screens like the retina iMacs. On some machines with older GPU's, it can be better to turn it off, but that won't hold true in your case.

Sync - yes, syncing from desktop to cloud in this case.  Click on the Activity Center, top left, and also see if Face Recognition and Map Locations are enabled or not.  (You should be able to leave them all enabled, but we're just trying to narrow down the cause of the issues.)
Photo of Stefan Redel

Stefan Redel

  • 87 Posts
  • 29 Reply Likes
It has nothing to do with Cloud, Face Recognition, GPS, GPU, ... (All disabled here together with newest drivers and GTX970 as GPU, 32 GB RAM, powerful CPU.)
Photo of David Efurd

David Efurd

  • 13 Posts
  • 5 Reply Likes
I confirmed that Sync, Map Locations and Face Recognition are all off.
Photo of Diko

Diko

  • 77 Posts
  • 9 Reply Likes
Here is my data. PLS note this is only LR currently running. Within those 10 min. I was processing images within LR only.



I can provide much more data if needed. What you see is only LR process running. I have a descent control on my win background processes and always throw an eye on my Process Explorer which is running always with admin rights. 

PS: And for some stupid reason I am hovering the two types of memory (instead of only the one). Sorry.

But never-the-less the beside the error still the trend of memory leak can be observed.
(Edited)
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 3696 Posts
  • 1196 Reply Likes
Interesting indeed. Were you active on the machine at the time?  What had you been doing?
Photo of Diko

Diko

  • 77 Posts
  • 9 Reply Likes
Processing Canon's 5Ds 50 MPx files, which already were converted to DNG files on a small catalog (both files and pics on SSD) while sitting on my Win 10x64, LR 6.6, 32 GB RAM, i7-6700K computer with Palit GTX 970.
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 3696 Posts
  • 1196 Reply Likes
Thanks. Does it continue to climb to crazy levels if you leave it running?
Photo of Kostadin Luchansky

Kostadin Luchansky

  • 22 Posts
  • 5 Reply Likes
On my machine the amount of RAM used by LR can (sometimes) grow up to 99% ot the total RAM (64GB in my case, iMac 5K, 27", late 2015, 4GHz i7, AMD Radeon 4GB Video, 1GB SSD). Happened on previous versions of LR too. I noticed that performance deteriorates faster and worse when Safari + Mail are both open as well. If I keep them closed, LR takes much longer to deteriorate (like 1h) until a close and reopen os needed.
Photo of Todd Shaner

Todd Shaner, Champion

  • 836 Posts
  • 252 Reply Likes
I can confirm the memory leak. I believe it's due to the change in 6.6 to that caches the Develop module previews for the image files adjacent to the currently selected file (i.e. 3 previews). Simply "browsing" images in the Develop module cause memory usage to climb and not be released. Use of the Adjustment Brush on multiple images is even worse. See this post: https://forums.adobe.com/message/8812806#8812806
Photo of David Collins

David Collins

  • 6 Posts
  • 3 Reply Likes

I'm also seeing my screen go black apart from the labels I have at the top of the image (exposure details etc) and then it comes back after up to 5 seconds.  Hasn't crashed yet - but feels like it will. 


Doesn't Adobe test these updates on a broader user base before releasing them?
(Edited)
Photo of Stefan Redel

Stefan Redel

  • 87 Posts
  • 29 Reply Likes
Done. Let's see if anything happens.
Photo of David Collins

David Collins

  • 6 Posts
  • 3 Reply Likes
Are we at an "uproar" point yet?
Photo of Paul Plak

Paul Plak

  • 138 Posts
  • 19 Reply Likes
Well I see those black screens too, then normal operations seem to resume after a few seconds.
Photo of Mark Hadden

Mark Hadden

  • 1 Post
  • 0 Reply Likes
black screens too
Photo of jeckylproductions

jeckylproductions

  • 8 Posts
  • 3 Reply Likes
Uninstalled and reinstalled CC 2015.5.1. It is running again without memory leaks or performance issues. I'll wait until a new patch comes out before testing the waters again.
Photo of Stefan Redel

Stefan Redel

  • 87 Posts
  • 29 Reply Likes
Solution: Minimize LR, wait 5 to 10 seconds, maximize, done. Then it runs fast (or slow...) as we are used to.
Try it.
Photo of Chris Pedersen

Chris Pedersen

  • 5 Posts
  • 0 Reply Likes
Just upgraded from LR standalone 6.5 to 6.6.

So far, I have never had any problems or issues with LR after an upgrade.

But after the LR 6.6 upgrade, it feels slower (I can't document it), and LR hangs if I start more than one export process at a time. And it is almost every time.

Also the screen turns black for a while when I move to another photo or do other actions. It just giving me a feeling that is not very stable.

My PC is totally up to date, Win 10 (64bit), 16 GB RAM, Nvidia GTX 980 with latest drivers.



(Edited)
Photo of Stefan Redel

Stefan Redel

  • 87 Posts
  • 29 Reply Likes
Minimize LR, wait 5 to 10 seconds, maximize it and you're able to work for another couple of pictures or actions. And then redo the procedure...

Or do it the best way: Downgrade to 6.5.1.
Photo of Jerry Syder

Jerry Syder

  • 181 Posts
  • 88 Reply Likes
Hi all. What I've done is uninstall all of my AMD products and reinstalled them(most importantly the graphic driver) and its working fine. As @stefan said, fast(or slow) as it used to. My rant is over :-)
Photo of Gethin

Gethin

  • 38 Posts
  • 6 Reply Likes
Moved  my cat and preview folders to a my fastest ssd (Samsung 950 pro). That did nothing so I moved my raw files (just one folder) to the same ssd.  Some improvement but still extremely laggy: taking 5 seconds to apply a develop preset for instance.  Applying and moving a grad felt like I was back on my i7 920 from 6 years ago.  Switching ON the graphics card improved grad speed, but it slowed down using the brush. WTF?   
Lightroom memory usage crept up whilst using it - 4gb to 12gb. over about 20 mins. 
I can also confirm that "turning it off and on again" helps with speed. 
Photo of David Efurd

David Efurd

  • 13 Posts
  • 5 Reply Likes
I've also noticed some graphical "ghosting" (not sure what to call it) where you can see some overlay of parts of the software when performing some step that I've never seen until now. For example, switching from Develop to Library module, I can see a faint, translucent box of something in the screen while it's switching over.  It pegs my CPU and takes about 5 seconds to come back to life and then the little translucent box disappears.  I also see crazy red flashes when adjusting the radial filter oval - I think it's related to the red coloring LR uses to show the mask.  It does it the first few times I adjust the filter and then they go away.  Trying to set white/black points (holding option key while sliding white and black adjustment sliders) is unusable to me now since it takes literally 3-4 seconds each time I move the slider and by the time it starts showing me parts of the image that are either white or black, I've already moved beyond it because of the severe lag. So frustrating.  It really feels like they didn't do any thorough QA/testing on this release.  I'm running what I think is a pretty standard computer setup for photo editors and I feel like I'm running a beta version of LR.  I thought I had actually found a solution which was turning off GPU in prefs, as things started acting normally again - everything was very speedy.  But that soon faded and after a few minutes, things were back to being very laggy with terrible performance so I enabled GPU again.  I'm going to try the suggestion above to reset my preferences file - I just haven't had time yet.  Hopefully that will cure the issues I'm having but I'm doubtful and really shouldn't have to go to those lengths to get a dot release working as it should.
(Edited)
Photo of Siddharth Sarkar

Siddharth Sarkar

  • 8 Posts
  • 1 Reply Like
please try smart previews i think it will be helpful for you ...........
Photo of David Efurd

David Efurd

  • 13 Posts
  • 5 Reply Likes
Not sure who that was directed to but I've been using smart previews since LR5. It isn't the cause of any of the performance issues I'm encountering.
Photo of Jeff Harmon

Jeff Harmon

  • 29 Posts
  • 38 Reply Likes
Lr doesn't use smart previews until it doesn't have access to the original files.  If you temporarily change the name of the folder where the original files are stored and then go through culling/develop module it will go significantly faster.  My testing has shown a 4x improvement in moving between photos.
Photo of Stefan Redel

Stefan Redel

  • 87 Posts
  • 29 Reply Likes
Solved it my way:
Uninstalled and reinstalled CC 2015.5.1. It is running again as we are used to.

BTW: Exporting in 2015.6 is a bit speedier. Never thought that. But Usability is what counts in this case.
Photo of Adam Rubinstein

Adam Rubinstein

  • 26 Posts
  • 4 Reply Likes
Yup. Same problem as everyone else. Moving between modules is terribly slow. Trying to drag out or move elliptical adjustments, LR lags hugely. Working exclusively with 20.2MP DNGs, for what it's worth.

Macbook Pro (10,2)
13" Retina
Intel Core i7 (2 cores)
8GB RAM
1536MB VRAM
512GB SSD
(Edited)
Photo of Assaf Frank

Assaf Frank

  • 147 Posts
  • 44 Reply Likes
4K display?
Photo of Mike Engles

Mike Engles

  • 26 Posts
  • 2 Reply Likes

Hello

Now, It seems that there is a validity in the many suggestions to stop work for 2 mins if the system becomes 'notchy'. I have done this several times and after resume, panning a 1:1 image at 1920x1200 is instant and no CPU howl, but seems to get worse in a few mins. Panning about does tax the system as it is continually processing and redrawing, rapidly changing parts of the image. Is there some sort of caching of view memory going on?

MDE

Photo of Frank Kollbrunner

Frank Kollbrunner

  • 1 Post
  • 0 Reply Likes
Seit dem neuesten Update ist das Lightroom leider sehr sehr langsam.
Bitte macht etwas daran, dass dies mit einem neuen Update wieder schnelle geht.
Photo of Hayley Green

Hayley Green

  • 2 Posts
  • 0 Reply Likes
Have you called Adobe?  The techs there ran me through all kinds of diagnostics and it really helped my speed.  It is worth a try.  Good luck!
Photo of George Gaab

George Gaab

  • 1 Post
  • 0 Reply Likes
I noticed a slow down with 2015.6  Some pictures taking a minute or more to load(.ORF) files. Disabled the GPU and things speed up!
Photo of m sadat

m sadat

  • 16 Posts
  • 9 Reply Likes
after spending hour with adobe on the phone and online, i went back to the previous version on their recommendation with gpu off, i just can't believe these guys roll product like this.