DPChallenge: A Digital Photography Contest You are not logged in. (log in or register
 

DPChallenge Forums >> Hardware and Software >> LR/CC latest version EXTREMELY slow
Pages:  
Showing posts 1 - 18 of 18, (reverse)
AuthorThread
07/10/2016 12:50:28 AM · #1
The latest LR/CC version was so slow...I'd also get blackouts (window gone, black in its place) for 4 - 5 seconds after requesting an operation.

Per the LR forum on Adobe's site, I reverted to the 2015.5.1 version (uninstall, then reinstall 2015, then update). Took about 10 minutes but totally worth it.

Let me know your experience with this. It's unacceptable that Adobe itself hasn't fixed this immediately.

(I'm a cc subscriber...but you can follow the instructions and even though you download and install LR 6's installer, it reinstalls to cc).

Instructions here: https://helpx.adobe.com/lightroom/kb/roll-back-to-prior-update.html
07/10/2016 09:38:22 AM · #2
Interesting. I've got 2015.6 in, and I'm not seeing this issue at all. Could it be because my machine is new, very robust and quick?
07/10/2016 10:41:15 AM · #3
Neil, sure sounds to me like a hardware-specific issue... Given the black window behavior, I'm left wondering if there is a graphics issue? Since you have reverted to an earlier version, no sense trying to troubleshoot. Did the Adobe forums give you any sense of where the commonality with others might lie?
07/10/2016 11:02:29 AM · #4
BTW, I'm a little wary because I was actually sitting down and installing the Lr/Ps CC apps this AM. I am leaving my CS6 installation alone, however.

ETA:
I finished the install, and did some brief playing around in Lr... the interface seems snappier than Lr6 on my machine, which is a pleasant surprise. I don't have any experience with the older versions of CC, this being my first experiment with the subscription. I suspect I actually have less hardware "horsepower" than you do, I know you tend to run high end systems due to your work. For reference my basic configuration is Win 10 insider preview build 14372.rs1 running on an i7-6700K processor, 32GB of RAM. GPU is an NVidia Quadro K1200.

Message edited by author 2016-07-10 11:28:18.
07/10/2016 12:06:18 PM · #5
Do you have the Use Graphics Processor checked? Probably a good idea to uncheck it (it's a resource hog). Also Lr tends to be a dog if your hard drive free space is more than 85% full.
07/10/2016 02:21:21 PM · #6
Originally posted by JakeKurdsjuk:

Do you have the Use Graphics Processor checked? Probably a good idea to uncheck it (it's a resource hog). Also Lr tends to be a dog if your hard drive free space is more than 85% full.


I did have it checked. I've just unchecked it, but of course, I don't have any problem with the 2015.5.1 version.

I also noticed in the .6 version that HDRs and Panos seemed to take forever compared to .5

But the worst was the "blackouts", where the LR window basically goes black for 5 seconds or so, if you try to do anything while it's processing HDRs. But that certainly isn't happening in this version, and I can do 5 or 6 HDRs at a time.

I have a very fast hex core I7 intel processor (i7 4930K @3.4GHz, benchmarks), 32GB of memory, and a GeForce GT 640 graphics card. 32GB Paging file on C. The system runs very well and for that reason, I haven't replaced it like usual, after a two-year cycle.

I have a 512GB SSD system drive which has a system partition and a large partition for data files, where the LR catalog is hosted. That has 55GB free of 208GB.

Actual photo storage is on large internal WD Black drives.

The LR catalog is 7.53GB and is optimized every few days, depending on use.

Here are threads showing others have the same problem:

https://forums.adobe.com/message/8815660#8815660
https://forums.adobe.com/message/8852354#8852354

kirbic - unchecking the use GPU box didn't make a difference according to other users. (I still unchecked it for now though.)

Someone else reports it on the Mac as well...and I recall reading complaints elsewhere from a lot of Mac users.

At least back on 2015.5.1 it seems fine for now. :)

07/10/2016 02:49:44 PM · #7
Neil,
When you were experiencing the slow performance, was it only after some time that it slowed down, or immediately? I see from your linked threads that there is a reported memory leak. That would imply that performance would only degrade after some time. I seem to be seeing the leak, after about 10 minutes Lr is using almost 9 GB of memory. Still performs fine at this point. As reported in the thread, minimizing the application and then un-minimizing it dramatically reduces the memory usage, in my case from 8.7GB to 1.7GB.
07/10/2016 03:20:48 PM · #8
Originally posted by kirbic:

Neil,
When you were experiencing the slow performance, was it only after some time that it slowed down, or immediately? I see from your linked threads that there is a reported memory leak. That would imply that performance would only degrade after some time. I seem to be seeing the leak, after about 10 minutes Lr is using almost 9 GB of memory. Still performs fine at this point. As reported in the thread, minimizing the application and then un-minimizing it dramatically reduces the memory usage, in my case from 8.7GB to 1.7GB.


Probably after a while, though I recall restarting LR at some point and I think it quickly went downhill. I shoot a lot of brackets, and my latest strategy is to use the wonderful HDR feature of LR and then delete either 2 or 3 of the originals, since the HDR "RAW" file is so good usually. That cuts down the number of files in my folders by 1 or 2 for each bracket set. So having that crawl, when it's already too slow since they try to run them all at once rather than queueing them sequentially, is not acceptable. Maybe that leaks even more!

I saw that about minimizing but went ahead and reverted because I don't think anything in the 2015.6 version was compelling enough to deal with the problem by constantly minimizing and waiting 4 seconds, when the prior version worked fine.

It only took about 10 minutes to downgrade and so I'll wait for 2015.7 and hope.

Message edited by author 2016-07-10 15:24:30.
07/10/2016 04:10:57 PM · #9
Originally posted by Neil:

I saw that about minimizing but went ahead and reverted because I don't think anything in the 2015.6 version was compelling enough to deal with the problem by constantly minimizing and waiting 4 seconds, when the prior version worked fine.

I'm in love with the new, excellent perspective-correction feature built into the new version...
07/10/2016 06:33:02 PM · #10
Originally posted by Bear_Music:

Originally posted by Neil:

I saw that about minimizing but went ahead and reverted because I don't think anything in the 2015.6 version was compelling enough to deal with the problem by constantly minimizing and waiting 4 seconds, when the prior version worked fine.

I'm in love with the new, excellent perspective-correction feature built into the new version...


It's great. I'm on a Macbook Pro (16GB RAM) and am having zero issues with 2015.6. I've got 25% free space on my disk and 25GB of memory allocated for Raw files. Having memory allocated and available seems to be the key since Lr 6/CC was released.
07/10/2016 07:04:38 PM · #11
Originally posted by Bear_Music:

Originally posted by Neil:

I saw that about minimizing but went ahead and reverted because I don't think anything in the 2015.6 version was compelling enough to deal with the problem by constantly minimizing and waiting 4 seconds, when the prior version worked fine.

I'm in love with the new, excellent perspective-correction feature built into the new version...


That was nice indeed...but I need it to work quickly with files first and foremost!
07/10/2016 10:22:50 PM · #12
Originally posted by Neil:

Originally posted by Bear_Music:

Originally posted by Neil:

I saw that about minimizing but went ahead and reverted because I don't think anything in the 2015.6 version was compelling enough to deal with the problem by constantly minimizing and waiting 4 seconds, when the prior version worked fine.

I'm in love with the new, excellent perspective-correction feature built into the new version...


That was nice indeed...but I need it to work quickly with files first and foremost!


You haven't mentioned your Camera Raw Cache setting. You've got 55GB available on the drive where the catalog is, but how much cache do you have allocated and is it on the same drive? A 7.5GB catalog file is HUGE, and regardless of where you have it stored and how fast that drive is that's got to be slowing you down as well. I break my catalogs up by year and even with a full year's images I'm not even close to 250MB for my Catalog file. I keep full sized previews around for 30 days and my current catalog is at 180MB with my preview file at 3.2GB.

I get that it's OK with 2015.5, but I wouldn't doubt that with a catalog file that big you're running into some limit somewhere.
07/10/2016 11:29:56 PM · #13
Originally posted by JakeKurdsjuk:

Originally posted by Neil:

Originally posted by Bear_Music:

Originally posted by Neil:

I saw that about minimizing but went ahead and reverted because I don't think anything in the 2015.6 version was compelling enough to deal with the problem by constantly minimizing and waiting 4 seconds, when the prior version worked fine.

I'm in love with the new, excellent perspective-correction feature built into the new version...


That was nice indeed...but I need it to work quickly with files first and foremost!


You haven't mentioned your Camera Raw Cache setting. You've got 55GB available on the drive where the catalog is, but how much cache do you have allocated and is it on the same drive? A 7.5GB catalog file is HUGE, and regardless of where you have it stored and how fast that drive is that's got to be slowing you down as well. I break my catalogs up by year and even with a full year's images I'm not even close to 250MB for my Catalog file. I keep full sized previews around for 30 days and my current catalog is at 180MB with my preview file at 3.2GB.

I get that it's OK with 2015.5, but I wouldn't doubt that with a catalog file that big you're running into some limit somewhere.


My cache is set to 50GB.

It's not a matter of image loading...it's a matter of the interface itself hanging up and not refreshing while it's doing something else. For example, if I were to have it filtered to not show deleted images, then I mark an image for deletion, in Develop mode, I would wait 4-5 seconds or more with the bottom thumbnail bar having a black hole in it or being improperly refreshed. Even just scrolling around in the thumbnail bar was a problem. Then, as I've mentioned, trying to merge photos using the HDR Merge or Panorama function would take it over the edge with just one item processing.

It's behaving like I would expect an app to behave if it were memory starved. Which it shouldn't be, with my 32GB of memory. Though I've seen LR complain before when there's plenty of system memory available, so it's likely some internal limit on memory allocation, combined with a memory leak or whatever, introduced in the new version.

I'm sure my big catalog isn't of any help. But since LR is not made for really working with multiple catalogs, it's not in my cards to split it up (though I've entertained the notion, but not being able to globally search multiple catalogs is a non-starter.

07/11/2016 09:02:57 AM · #14
this is interesting...it might also explain some of my problem since as well as HDRs I have fairly large panoramas in my thumb strip.

"A big change in .6 is to pre-loading images. Develop should be faster when you initially take a picture into it, and Lightroom then loads into RAM the 2 images before and 2 images after the current image, so when you navigate in either direction you should see loading time improvements."

In other words, the problems I was having scrolling around the thumbnail strip could be very slow loads of larger file previews, along with a memory leak.
07/11/2016 11:16:26 AM · #15
Question...what screen resolutions are you guys running?

I am running 2560x1600 pixels on my primary regular monitor and 1680x1050 pixels on a secondary wide gamut monitor (NEC P221W)
07/11/2016 11:28:27 AM · #16
I love it when ya'll speak Greek geek!!!
07/11/2016 12:02:15 PM · #17
Originally posted by Neil:

Question...what screen resolutions are you guys running?

I am running 2560x1600 pixels on my primary regular monitor and 1680x1050 pixels on a secondary wide gamut monitor (NEC P221W)


I'm only running one monitor at the present time, and it is running at 2560x1440. Planning on some 4k deliciousness within the next 12 months or so :-)

ETA: I should add that my single monitor is wide-gamut (Dell U2711).

Message edited by author 2016-07-11 12:13:05.
07/11/2016 12:06:16 PM · #18
2560 x 1440 here... ViewSonic 27"
Pages:  
Current Server Time: 04/18/2024 09:58:06 PM

Please log in or register to post to the forums.


Home - Challenges - Community - League - Photos - Cameras - Lenses - Learn - Prints! - Help - Terms of Use - Privacy - Top ^
DPChallenge, and website content and design, Copyright © 2001-2024 Challenging Technologies, LLC.
All digital photo copyrights belong to the photographers and may not be used without permission.
Current Server Time: 04/18/2024 09:58:06 PM EDT.