Progress bar for background tasks needed

  • 2
  • Idea
  • Updated 1 day ago
Moving the mouse just got jerky and I find that Lightroom is using 25% of a 6-core Xeon processor for no reason that I can determine. I'd just finished editing 11 photos and deleting about 40-50 spread over a half an hour. 3% GPU but only 14.5 GB of RAM out of 64. If it is working on the XMP files, shutting down will give a warning message but that isn't happening in this case. Shutting down and restarting dropped the CPU to under 1%. 
 
Sometimes building previews has a progress bar, perhaps most of the time, but not always. I'd just like to see a progress bar whenever Lightroom is performing some background task with a meaningful label. After all, it knows that it is performing the task. 
  
Photo of Bill

Bill

  • 252 Posts
  • 36 Reply Likes

Posted 4 days ago

  • 2
Photo of Gary Rowe

Gary Rowe

  • 132 Posts
  • 43 Reply Likes
Would be a very welcome addition to LrC
Photo of John R. Ellis

John R. Ellis, Champion

  • 5113 Posts
  • 1447 Reply Likes
If you can narrow down which tasks might be causing the CPU usage or what kicks off this behavior, that could help. In general, LR does try to show progress bars for long-running tasks, so it's possible you're encountering a bug (something taking a long time due to a bug), or it could be that it's one area of LR where the developers forgot to include a progress bar.  
Photo of Bill

Bill

  • 252 Posts
  • 36 Reply Likes
How can I narrow down the tasks if they are internal to Lightroom and not exposed for our view? For example, Lightroom does not show a progress bar while updating xmp files or when rebuilding previews. 
 
So Lightroom developers, fewer secrets please. 
 
Photo of John R. Ellis

John R. Ellis, Champion

  • 5113 Posts
  • 1447 Reply Likes
See if you can associate the high CPU with recent actions, e.g. does it occur after imports? After deleting a collection? For better or worse (mostly worse), I don't think Adobe will take any steps to improve this without knowing which actions are not using a progress bar.

I remembered one activity for which LR doesn't show a progress bar: indexing faces. You have to look in the Identity plate to see that:







Photo of Gary Rowe

Gary Rowe

  • 132 Posts
  • 43 Reply Likes
No doubt you are right that Adobe won't make any changes, but I'm scared by your thought that Adobe don't already know the places where LrC processes in the background without telling us.

When my system slows right down, it's really annoying to have to go off and find that it is, yet again, LrC that is the resource hog; if it told me it had work to do, I'd give it the time, but doing it silently just pisses me off.

It isn't much to ask for, but sadly paying them every month doesn't seem to mean that they do something every month.
Photo of John R. Ellis

John R. Ellis, Champion

  • 5113 Posts
  • 1447 Reply Likes
Don't shoot the messenger for this, I'm just providing my observations from a decade of contributing here:

Adobe does make changes and improvements, but at a very slow pace. Feedback from users here is one way they prioritize their efforts.  A few posts from a few people about a general issue without specific details is unlikely to influence them.  Unless dozens or hundreds of people are providing complaints or votes for a feature or improvement, Adobe developers are unlikely to put much thought into investigating an issue, and you generally have to provide very specific details or step-by-step recipes to influence them. (I and other volunteers here, along with a couple of employees, do try to coalesce similar posts to make it more likely they'll have influence.)

In this instance, I don't think a few posts that Adobe doesn't always show progress bars when LR is doing something in background will have much impact. If there were dozens of people commenting and voting about it, that might be different.

On the other hand, a very specific feature request, such as, "LR should show a progress bar when doing face recognition", accompanied with details about why that matters to your workflow, even if it has just a handful of votes (or just one) is more likely to influence Adobe.  

Or, "In the following circumstance, LR fails to put up a progress bar when building previews in background. Here are steps for reliably reproducing the problem..." I've filed many such reports, and Adobe has acted on some of them, even if they have just one or two votes.

If you're not sure about what's causing the background activity (a bug or an oversight in providing a progress bar), or you don't know how to reliably reproduce it, then posting here as Bill has is still worthwhile, so that complaints from others might have a place to get merged into and eventually establish a pattern that Adobe is most likely to notice. But in this case, where it's likely that the problem behavior has been around for a long time, the likelihood that there will soon be a dozen or more votes is pretty small, in my opinion.
Photo of Bill

Bill

  • 252 Posts
  • 36 Reply Likes
Scan for the large number of posts complaining about high CPU consumption and you'll have no shortage of folks who want to know what's going on in these situations.    
Furthermore a secret long running task is not always using a lot of CPU. It can still be working correctly and efficiently, updating a large number of XMP files for example. 
  
Guessing games as a solution is neither useful, practical nor accurate. Easily the number one complaint about Lightroom is performance, frequently unjustified. But how can we tell when the activity is a secret. 
  
The limited number of progress bars is the closest we get to a Lightroom Performance Monitor. 
 
So Adobe, either enhance the progress bars or give us a performance monitor. Currently our only option is to call the Physic Hotline. 


Photo of Bill

Bill

  • 252 Posts
  • 36 Reply Likes
I already gave you two that I've discovered.