Lightroom 6 / CC2015: Very slow UI response with background export(s) running

  • 45
  • Problem
  • Updated 9 months ago
Lightroom 6 / CC2015s UI reaction is very slow / sluggish when a background export is running. When three exports are running, the development module becomes virtually unusable.

In Lightroom 4 or 5 it was no problem at all to start up to three or four background exports - of course the UI, especially the development module, was considerably slower than normal, but definitely completely usable.

LR Version: CC 2015.0.1 (with 6.0.1 update), on Window 7 64. Processor is an i7-2600, there is 16 GB RAM. RAM does not seem to be exhausted, LR6 uses about 3...4 GB with 3 parallel exports.

Edit: It makes no difference whether GPU usage is turned on or off.
Photo of LRuserXY

LRuserXY

  • 426 Posts
  • 41 Reply Likes

Posted 3 years ago

  • 45
Photo of Dieter Karner

Dieter Karner

  • 2 Posts
  • 0 Reply Likes
LR6 seems to speed up when I pause face detection and address lookup.
Photo of Richard Scheibe

Richard Scheibe

  • 7 Posts
  • 0 Reply Likes
I've found the same; pausing face detection and address lookup seems to help. The long pole on the import function is converting to DNG; it seems to take longer to convert. Since I don't have a 5.7 version any more it is hard to test the difference.
Photo of Richard Scheibe

Richard Scheibe

  • 7 Posts
  • 0 Reply Likes
My system (IMac, 10.10.3, 3.06 GHz Intel Core 2 Duo) takes ~ 32 seconds/image to import, convert to DNG, and build standard previews (2880) of Fuji (RAF) files. According to the Activity Monitor, both cores are running flat out to do the work.
Photo of Denni Russel

Denni Russel

  • 43 Posts
  • 9 Reply Likes
So, Adobe has a senior engineer commenting like crazy over on the PS windows hidpi scaling forum. And yet here we still have nothing - not a single word - from Adobe. And nothing so far in the industry media about this.

Adobe, if you are reading these posts, PLEASE join in the conversation.
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 813 Reply Likes
The LightRoom team is quite busy right now.
Photo of Denni Russel

Denni Russel

  • 43 Posts
  • 9 Reply Likes
Chris, I don't think anyone necessarily needs an engineer or programmer to give us blow by blows. I'm actually quite glad the LR engineering team is busy. I'm sure we all are. That said - and I hate to sound snarky - the project mangers should have created some sort of mechanism for communicating with the customers some time back in the 1980's. There should be a client relations team. Other companies have been known to create things like that. If the LR team really is too busy, and if Adobe really doesn't think it has an issue in the way it handles these sorts of major release snafus, then the problems go far deeper than a lousy software release. Perhaps it would be even better if software engineers weren't the ones handling these customer interactions. The constant refrain 'everyone at Adobe is too busy to help you' is more than a little insulting.
(Edited)
Photo of Denni Russel

Denni Russel

  • 43 Posts
  • 9 Reply Likes
You know what, I'll do it for Adobe (free of charge). Just cut and paste this on your site then put out on an email blast:

'To all our loyal customers, we are sorry to report that Lightroom 6/CC, in its current version, has major structural flaws. As such, we strongly recommend not upgrading from version 5 until such time as we can solve this temporary problem. We sincerely apologise for this unforgivable delay in admitting the problem and will be offering a rebate to those whose businesses have been negativity impacted by this situation.'
Photo of Denni Russel

Denni Russel

  • 43 Posts
  • 9 Reply Likes
Last thing - Chris, I do appreciate you engaging. My frustration isnt directed towards you.
Photo of Diko

Diko

  • 77 Posts
  • 9 Reply Likes
Well said, Denni.

Adobe main concern for sure is the communicating part... I am pretty sure we all got out of the nerdy state of the 80s & 90s and now we all use computers and we all know how to communicate.

Obviously someone @ Adobe is still along the old ways ;-)
Photo of JOHN NELSON

JOHN NELSON

  • 5 Posts
  • 4 Reply Likes
There is a bigger problem then the heading would lead you to believe. I'll say again. I bought a new machine just for this version. i7, GTX980, 32 gigs, NEC 30 II, on and on. I started this machine up and installed the old (5.7) and then "LR6" and had problems out of the box...there is a problem for sure. I'm also about to take my LR certification as soon as they make up the darn new testing schedule. I understand that there's a problem a little more then most. Many of the problems I've seen have nothing to do with "working in the background" (although a problem). Something I never do BTW. But if I load up the software with a multi layered file I can kiss it goodbye after a while. I also work with OnOne and PS. I'm talking 10-15+ layers. Say its on a virtual copy. If I go back to the original copy it "may" work fine and not slow down. There are multiple layers of problems. So...you may use LR "lightly" and not see a problem and say>>>>"well I don't have a problem" but when you push the program...it does. I went onto another person's system with the same file I had a problem with...then started to do the same work on it. After a while....poof...there you go. It bogs down. Different system but it still loaded up and slowed down. Guessing something to do with the way the cache/ram from card is handle...beyond me though. As ealier...my solution was to just start a new Cat. in 5.7 CC till they fix. 5.7 works perfect on the same machine....same file that was merged into LR6 CC...works perfect and lightning fast.

I did have somebody say that they talked to a rep and that person said there is a problem for sure. But that is second hand. I feel sorry for all the people that are struggling and trying to fix it and Adobe will not acknowledge and just lets them keep on looking for a solution that is not there. That is the part that really seems to suck. I'm lucky...I have 5.7.
Photo of DOUGLAS FAIRBAIRN

DOUGLAS FAIRBAIRN

  • 1 Post
  • 2 Reply Likes
I wrote a letter to the Adobe CEO and told him to withdraw this awful product from the market and apologize to the user base.
Photo of em vaningen

em vaningen

  • 68 Posts
  • 6 Reply Likes
Did you get any reply ?
Photo of Diko

Diko

  • 77 Posts
  • 9 Reply Likes
Really did they address your letter in any way?
Photo of em vaningen

em vaningen

  • 68 Posts
  • 6 Reply Likes
I went back to 5.7 as well, despite the absence of a reverse the database tool. Even though I have 1:1 previews, it takes 30 seconds to display a oictre, Same picgture in ViewNX takes a split second.

Wasting my time with LR CC,
Photo of em vaningen

em vaningen

  • 68 Posts
  • 6 Reply Likes
On my desktop, CC runs much better.
I am at loss why it is UNUSABLE on my laptop (which runs 5.7 very well)

Desktop Laptop
I7 I7 (I know that not all I7 are the same but I can't recall the exact
8GB 6GB
AMD Nvidea
Photo of Łukasz Struk

Łukasz Struk

  • 2 Posts
  • 0 Reply Likes
After yesterday's update of Lightroom CC and CC apps I can really work again.
It works really good.
Photo of em vaningen

em vaningen

  • 68 Posts
  • 6 Reply Likes
Any performance improvements are not mentioned by ado be. Just the new slider, as if that more important or time waiting for picture load.
(Edited)
Photo of Andy Richards

Andy Richards

  • 5 Posts
  • 0 Reply Likes
Great, A new slider. If only I could load my images...
Photo of Jim Watts

Jim Watts

  • 1 Post
  • 1 Reply Like
Well the June 16th cc2015.1 has proved a diaster for me. I had finally, with difficulty, just got version 6.1 running at an acceptable (but not as good as 5.7) speed by using all the recommendations, but now it is virtually unusable again. After 10 minutes use in the Develop module it virtually grinds to a halt. Sliders not responding in real time and each image taking ages to render. Now if I try to go from Lightroom to Photoshop with 'edit in' it tells me it can't open Photoshop as it needs Windows 7 64bit to run? That's hat it is running on!

Checked all the previous recommendations. Disabelled GPU etc. Makes no difference at all. Reloading Lightroom speeds it up for about 10 - 15 minutes and then it slows again.

Windows 7 64bit on PC with i7 cpu, 32 gig ram, SSD for programs & catalog only.

I have had to revert to 5.7, but beginning to think it's time to ditch Adobe completely and buy Capture One. Can't see any reason to pay a subscription for updates that make the programme unusable.
Photo of Brent Rivers

Brent Rivers

  • 10 Posts
  • 0 Reply Likes
and this is not OS specific issues either, looks to be across the board for both windows and osx. I finally had to devote some time researching thinking it must be me, and i'd obviously missed the memo on settings after upgrading. stupid me jumped in with both feet leaving LR5 all together and moving entire catalogues. now i'm stuck. I really don't want to move to C1, not unless it's a must do. I may have to change workflow until this gets resolved.
Photo of Diko

Diko

  • 77 Posts
  • 9 Reply Likes
I think this sluggishness has something to do with the RAM managment and allocation processes within LR
Photo of Gerhard Krischker

Gerhard Krischker

  • 1 Post
  • 0 Reply Likes
I am also a Pro. I tell everybody Lightroom is my workhorse. And how great the program is(was?) But now its a veeery slow and old workhorse. Why creative cloud tells my all the time to upgrade and then I have slower product afterwards. Please ADOBE help us with the Problem.
Photo of Brent Rivers

Brent Rivers

  • 10 Posts
  • 0 Reply Likes
not sure if Chris Cox is monitoring this thread, or other similar threads, but for those of us who have been with LR for quite a while, it'd be comforting to know that there is an acknowledgement from Adobe that there is an issue, and, that it's being worked out ever how long it takes. Otherwise, i'll have to look for other solutions. I'm basically hampered in conducting business with exporting and publishing issues. I can work "ok" within develop as long as GPU is unselected, but there are obviously real issues facing many different platforms. I'm on a kick arse macbookpro with all the goodies, I can crunch out video with no issues and use a 4 SSD drive raid 0 thunderbolt2, so I know i can still handle still images for years to come. Let's get these things updated either with an acknowledgement, or, an actual update...thanks Adobe!
Photo of Denni Russel

Denni Russel

  • 43 Posts
  • 9 Reply Likes
That's just it, isn't it. Adobe's lack of acknowledgement leaves us all in a lurch. I've just bought Capture One and am trying to move my workflow over that way. I've used LR since it was in beta. I teach LR at two colleges and am responsible for software recommendations for both photography departments. If I don't hear something concrete from Adobe soon we're going to have to purchase Capture One for our school computers. We have CC subscriptions for all the systems, but I'll be forced to re-write the curricula to incorporate CO and leave out LR.

I think Adobe is so focused on mobile apps and adding new features that they simply don't look back - even when they've broken a flagship app like LR.

The directors are telling the developers to work on new things and they simply aren't putting any effort into the complete overhaul of LR that is obviously required. If this were a small problem Adobe would have acknowledged and addressed it. But my guess is that it's too big for them to admit. And so they're putting their fingers into their ears and collectively saying to us 'we can't hear you'.

What I don't understand is the silence on the issue from Kelby's Krew. Where are the industry mouth pieces on this? Have any of you read anything in the industry media?
Photo of Denni Russel

Denni Russel

  • 43 Posts
  • 9 Reply Likes
I agree with you 100%.
Photo of em vaningen

em vaningen

  • 68 Posts
  • 6 Reply Likes
Agree
Photo of Diko

Diko

  • 77 Posts
  • 9 Reply Likes
Exactly! As I said - Adobe is still lacking social skills :D :D :D Or maybe not?

The core of the issue is that a few of us googled this thread and began whining and complaining.

As long as the top main LR / PS / Adobe Bloggers don't complain enough to bring the attention of the crowds to these particular bugs and issues discussed here Adobe won't make a move.

The average Joe is either not complaining but directly moves to CO (or whatever program that is applicable to his/her workflow), or he/she thinks that it's because of his/her computer configuration and there is no chance that the Adobe almighty has screwed it up.

If you happen to know a widely known, popular or decision leader and blogger. Let him read this thread and write something.

Obviously it's the same as the commercial photography:
20% Photography - 80% Business.

In their case:
20% Development - 80% Marketing
Photo of Housik

Housik

  • 22 Posts
  • 2 Reply Likes
Pareto principle, you are right! https://en.wikipedia.org/wiki/Pareto_... :-)
As you said, Adobe please stop add features and start to optimize LR. Try to get maximum from CUDA and similar technology. A lot of us has integrated GPU and Nvidia GPU, why not try to use both?

Russian developers are able to use graphics cards for cracking wirelless communication between key and vehicle. So Adobe please try to use GPU to speed up graphics operations in LR. I know, you are trying, but it is funny, when I check GPU acceleration and whole development module slow down. This is not the goal...
Photo of Diko

Diko

  • 77 Posts
  • 9 Reply Likes
GPU utilization in my case (GTX 970) - never exceeds the 3%... :-(

PS: The more I live the more I see Pareto principle more and more. Unfortunately for me I got to know it some time ago already.
Photo of em vaningen

em vaningen

  • 68 Posts
  • 6 Reply Likes
I am now working on my destop (Acer with I7, 8Mb and only AMD Radion 8570, 2Mb) and performance is acceptble afer the recent upgrade.

Have to check why my laptop (I7) is so significantly slower.

My Q remains, why is viewNX2 (Nikon) so much faster in rendering full size (unedited)
Photo of michaelcharvet

michaelcharvet

  • 1 Post
  • 0 Reply Likes
Wish I'd found this thread before updated to CC. What a dog. LR is dramatically slower and ponderous compared to 5.x versions, almost unusable.

I have a real problem with Adobe's Cloud. Ostensibly designed to bring to latest features and experience to users, I take that view that it's really driven by Adobe financials. Users are obliged to pay monthly, forever, if they want to use the apps.

Iif those apps are buggy or don't perform, that's too bad. Do you really want the latest software? I don't. 30+ years of using PC's has taught me to never buy the latest of anything. If you want a stable production experience, stick with proven versions until it's safe to move on.

Adobe's approach smooths out their cash flow while forcing unwanted features and problems on users. No thanks!

I canceled CC, convinced Adobe to waive their "early termination fee" (just like the phone companies!), and I'm back to earlier versions. But now my old Acrobat won't install, so I get to spend more hours figuring that out, and maybe re-installing my operating system.

Folks, it's time to consider alternatives. Capture One comes to mind.

I hate the Adobe Cloud. Hate it.
Photo of Brent Rivers

Brent Rivers

  • 10 Posts
  • 0 Reply Likes
this isn't a "cloud" issue, this is an issue with professional level tools that release, with many, many issues. The "cloud" in terms of functionality, is data storage and access. Very little out there actually runs in "the cloud". The days of my data being locked down on a spinning local drive that's destined to crash any minute, are over, and thank goodness. But I did get into Adobe's SAS model (software as a service) which has nothing to do with cloud computing. The cool thing is, for anyone that's on the 10 bucks a month plan, they can bug out of this thing any time, so Adobe is certainly incented to release features AND functionality, or suffer the loss of revenue streams and ultimately clients. I did price out C1's sas model and it's too expensive for what you get.
Photo of Denni Russel

Denni Russel

  • 43 Posts
  • 9 Reply Likes
Capture one is $15/month subscription and $300 to buy. Not cheap... But less than a camera battery ;).
Photo of Diko

Diko

  • 77 Posts
  • 9 Reply Likes
"I did price out C1's sas model and it's too expensive for what you get." - Could you please elaborate a little?

I don't understand what you mean. Really.
Photo of momentsindigital

momentsindigital

  • 3 Posts
  • 0 Reply Likes
Is there anyone from Adobe who actually follows these forums and has the authority to chime in on these major issues?

As a working professional wedding photographer heading into the busiest time of year, I simply can't afford to have these slowdowns in our workflow. Everything from importing, exporting, local adjustments, browsing, cropping, etc is slower than previous versions of LR despite your claims of improved performance as a result of using the GPU.

Unacceptable Adobe. I too am considering other options such as CaptureOne if you guys can't get it together. At the very least be transparent and let your users know what is going on. Clearly there are issues as evident from the comments in the forums yet silence on your end.
Photo of Steve Sprengel

Steve Sprengel, Champion

  • 2632 Posts
  • 337 Reply Likes
Adobe is a publically traded company and will likely not be "transparent" about internal things. Adobe cannot acknowledge LR 6 is slower on your specific computer because they don't have it in house for testing.

I imagine you have the option of using LR 5 if you feel it is faster.

The GPU helps with HiDPI/Retina displays that were horrible with CPU-computed images. It helps less with lower-res displays or can actually be slower. I have the GPU disabled on my several-year-old computer because it is much slower--the video card and the bus-speed are too slow. I can enable or disable the GPU on my less-than-2-year-old system and it is similar so I probably leave it disabled if I'm using PS in addition to LR so PS can have exclusive access to it.

Something must be a bottle-neck on your system that makes LR 6/2015 slower than it is for most people. Adobe doesn't purposely release software that is slower than it's predecessor on their own systems, but that doesn't mean it's faster for every single computer configuration.

Updating video drivers and disabling virus/internet-security software, rearranging what drives have what LR components on them, are things some people have had success with.

If you're on Windows, you can speed things up by setting the main LR process priority to below-normal, which lets some of the background threads have more resources. The way to do that is to create a LR shortcut that looks like this:

C:\Windows\System32\cmd.exe /c start "Adobe Lightroom" /belownormal "C:\Program Files\Adobe\Adobe Lightroom\lightroom.exe"

You will lose the ability to drag-and-drop to the open LR process, so you probably want to make this a second shortcut for LR, and leave your original one for when you're doing D-n-D imports if that is applicable.
Photo of Steve Sprengel

Steve Sprengel, Champion

  • 2632 Posts
  • 337 Reply Likes
Somehow my computer runs LR 6 just fine. I do have all my photos and catalog on a USB3-attached drive on Windows 8.1 on a Dell computer built Dec 2013, so it's possible something related to I/O gets in the way of other operations on computers with SSDs or cached hard-drives that have faster I/O and on my computer the I/O is slow enough that it doesn't get in the way.
Photo of Andy Richards

Andy Richards

  • 5 Posts
  • 0 Reply Likes
Sorry Steve, can't agree with you. This slowdown doesn't happen on LR 5.7 on the exact same system, move to CC and it's a sloth. That's not easy to just dismiss as a hardware issue.
Photo of Steve Sprengel

Steve Sprengel, Champion

  • 2632 Posts
  • 337 Reply Likes
The sloth has not visited my system, then.
Photo of JOHN NELSON

JOHN NELSON

  • 5 Posts
  • 4 Reply Likes
...way above you'll see I bought a new system. 32gigs of RAM and the rest to go with it. This is not just running slow. I never see the problems until I really tax LR. I mean about 40+ layers back in from PS. CRASH, flashing screen, missing or loosing edits. Like I said the system was bought NEW just to edit with. Plus two 30" NEC monitors. Been working with Adobe since the 90's. I loaded 5.7 and worked my cat. like normal and then converted to 6. Thought it was working great until I really started pushing it. Back and forth to PS and OnOne. LR on a sep internal drive. OS on SD. Fast fast fast. But maybe that is why I don't see the problems until I really push it. I do not work with a bunch of images but really edit on each prime image. I teach and storm chase with a bunch of photogs and many of the people are having problems BUT they all like myself just keep saying....I'll wait till they get it fixed. We keep using 5.7. But they are the ones that are also pushing the system. Also I've talked to people that have been with Tech support and they have begrudgingly admitted that there is a problem and there was not a fix for now. I never could find out was "it" was. So to put it simply....there is a problem. I should be able to buy a new machine and make it go with out a problem or any "fixes". I've checked everything and I can't find a hint of a conflict. Endless days of making sure no conflicts. Reinstalling. Going into reg and looking for old files. NOTHING! and nothing Adobe can find. Remember a NEW machine. They have been on my machine. I'll stick with 5.7 as it is smoking fast with this new machine and NEVER crashes. NEVER!!!!!! ....even on my old machine that this one replaced. BTW...it does have many of the same problems on my older WIN 7 64bit Laptop (16 gigs) that also runs 5.x perfectly. BTW....GPU on off....no difference.

For me the answer is to leave what has been done with LR6 (CC) Start a new in 5.7 and will import into 6 when it is up and running for sure.
Photo of John Gannon

John Gannon

  • 10 Posts
  • 2 Reply Likes
This didn't accomplish anything except add to my frustration.

Clearly, by the number of responses on this thread alone, there is a problem.
Photo of Andrej Stern

Andrej Stern

  • 7 Posts
  • 1 Reply Like
I work with a i7@3.4GHz, 16GB Ram, SSD and GTX960 4GB. My camera is a Nikon D800, so the files are pretty big. But Lightroom 6 is horribly slow when I edit a photo. Example: I drag the exposureslider and the changes appear two seconds later, which is extremely annoying. This way, you can't quickly make small adjustments.

Working with Lightroom becomes more and more annoying.
Photo of Diko

Diko

  • 77 Posts
  • 9 Reply Likes
The "good solution" was for the last sentence, with which I agree to full extend.
Photo of howard

howard

  • 1 Post
  • 0 Reply Likes
I'll add my voice to this chorus.

I am going to try going back to 5.7.

The extra features on 6 are not worth the hassle.
Photo of Lew Tarnopol

Lew Tarnopol

  • 1 Post
  • 0 Reply Likes
I, too, will add my voice. I'm in the midst of exporting 1000's of jpgs for a set of children's dance recitals (actually, 25 different recitals across 2 days - post was a bear) and LRCC 2015 is a real pig. Just starting up one export of 75 jpgs pretty much freezes the UI. Trying to start a second or third export as I once did is a joke.

My system is a new Mac Pro (late 2013) with a 6-core Xeon E5 and 64GB of RAM, with an AMD FirePro D500 driving an NEC Multisync PA272W. My external drive (where all my images are kept) is a 4TB RAID 0 thunderbolt. The internal HD is a 1TB SSD. That's where the LR catalog and previews are kept. So, there h'aint nuthin' wrong with my hardware. I used to process exports 5x faster on my old 2010 iMac with LR3 and LR4.

No other memory hogs are running (for example, Photoshop). In fact, I did a clean reboot before starting to export any jpgs, just to be sure a max amount of CPU and memory would be available.

Please, Adobe, fix the export performance issues!

Sigh.
Photo of John Gannon

John Gannon

  • 10 Posts
  • 2 Reply Likes
I don't know what has happened but over the past few weeks my workflow has diminished tremendously. I can't even work on photos at this point. Simply switching photos at this point is causing a problem.

So frustrated right now. I've been using Lightroom for years and never once had a problem.

What the did you guys do with Lightroom?!?
Photo of PhotoCoq

PhotoCoq

  • 3 Posts
  • 0 Reply Likes
i7, 8 Gb Ram, plain Intel HD Graphics 4400
After upgrade from LR4 everything went so slooooowwwww (and even slower)
Went to preferences/ perfomance and disabled the use of GPU.
Now faster and similar to LR4 performance ... which unfortunately aren't tremendous.
Photo of Michelle Gilders

Michelle Gilders

  • 4 Posts
  • 0 Reply Likes
I will add my frustration to the list. It seems like I can work on about 6 images, either in Library or Develop mode, zooming in at 100% of check sharpness, then when I go to the seventh image or so, it spends loads of time loading the next image...sometimes several minutes. And this despite the fact that I built 1:1 previews on import. It is becoming unusable. i think I'm going back to 5.7 until they fix this. Even grinds to a halt when I select multiple images and try to add captions.

Windows 7 Professional. 16 Gb RAM, i7, 64 bit
Photo of John Gannon

John Gannon

  • 10 Posts
  • 2 Reply Likes
Has Adobe even acknowledged this, or is it radio silence?
Photo of em vaningen

em vaningen

  • 68 Posts
  • 6 Reply Likes
i asked the same question some time ago. Still don't know if Adobe even reads this
Photo of Denni Russel

Denni Russel

  • 43 Posts
  • 9 Reply Likes
Then Chris, why oh why, is what you just wrote the first -and only! - written acknowledgement from Adobe?
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 813 Reply Likes
Because there are multiple topics going on about issues, and the LR team is kind of busy fixing issues. I post on here while I'm waiting for compiles to finish, or stuff to download.
Photo of John Gannon

John Gannon

  • 10 Posts
  • 2 Reply Likes
Chris, I'll be contacting your boss directly. Thank you for your time.
Photo of Brent Rivers

Brent Rivers

  • 10 Posts
  • 0 Reply Likes
Chris, as you can imagine, when there's money at stake, it's a different response than if it's a superficial issue. We appreciate Adobe working to correct issues with the latest release, but you may want your PR dept to step out to address concerns, list out efforts, and maybe, just maybe issue a timeline as to the next update. If we use pure statistics, I suspect it's affecting more than 40% of your user base. Many just plod along not going to forums for help. Obviously there are no personal vendettas here, just looking for answers. We've grown dependent on the technology to sustain our livelihoods through business...
Photo of John Gannon

John Gannon

  • 10 Posts
  • 2 Reply Likes
I tried that Brent, he removed my comment because it wasn't helpful.