LR4.2 not addressing performance? Oh noes!

  • 1
  • Problem
  • Updated 7 years ago
Merged

This conversation has been merged. Please reference the main conversation: Lightroom: LR4.2 Performance Issues remain

Morning all. I have LR4.1 and love it. Well, want to love it. It is so much better than 3 at developing, making books, etc etc.

But oh my giddy aunt it is SO SLOOOOW* :-(

Running Win7 on i3 with 8Gb RAM, 1080p LED 2ndary monitor. Not the best setup in the world, granted, but LR3 flew on it. LR4 is like going back 5 years in time.

I assumed you were working on fixing this, but when I saw your response to speed complaints for the 4.2RC that "no-one is complaining about speed" I realised I needed to make a profile, log in, and let you know. Please oh please fix the performance issues.

The weird thing is that CS6 runs way faster than CS3 did, on the same hardware. LR4, h3ll no.

LR4 is lightyears (haha) ahead of LR3 in terms of features and what the pics look like coming out of there. But. it. is. so. slow.

Andy

* Main speed issues are:
- going to and from Develop module from grid view. I get a black bar at the top of the screen, so I go make coffee and wait for it to come right.
- the preview pane top left takes so long to update when hovering over a preset that I don't bother to use it any more
- during use, everything just slows down (memory leak?) so I reset my machine every tea or coffee break to keep the performance going. Never had to do this with LR3.
Photo of Andrew

Andrew

  • 2 Posts
  • 0 Reply Likes
  • frustrated

Posted 7 years ago

  • 1
Photo of jdv

jdv, Champion

  • 728 Posts
  • 56 Reply Likes
Have you done /any/ of the steps outlined in the long thread related to the typical performance problems people are having?

That being said, what you report does not sound like what other people are seeing. I think you have slightly unique problems related to your installation or your system.

1. going to and from Develop module from grid view. I get a black bar at the top of the screen, so I go make coffee and wait for it to come right.

I assume you mean the standard module picker (I hide this, so I'm just guessing) or perhaps you mean the menu bar? Either way, this really has nothing to do with the images or data you are working on, but is a problem with the app updating the viewscreen, or the Lua code in the UI stalling.

There is no easy way to tell without some advanced diagnostics, though. You will want to make sure your (2D) video drivers are up-to-date. If you know how to use some of the diag tools in Windows 7, you can check to see if you can get a sample of the process while it is spinning.

2. the preview pane top left takes so long to update when hovering over a preset that I don't bother to use it any more

This could very well be related to the same problem as (1), with the viewport being slow to update. Or it could be how Lr is fetching and using the preview cache. Have you recreated your standard previews, as per the other thread?

This may also be a place where the ACR cache comes into play (this is a guess), so you might want to purge that, and make sure it is sized higher (e.g., 50Gb is good start). This certainly cannot hurt to try, and it has solve all sorts of problems for others.

This is the time to think about where the ACR cache is, and to see if you can move it to a different physical volume than the catalogue so that disk I/O contention is minimized.

3. during use, everything just slows down (memory leak?) so I reset my machine every tea or coffee break to keep the performance going. Never had to do this with LR3.

The only way to know what is going on is to match up specific behaviour (what module, what specific activities) with hard evidence gathered from the Win7 diagnostics tools. Again, the advice given above might just fix this, if you are talking about Develop module and the ACR cache, or some other module and the preview cache.

Suggestions:

- Try running Lr from a new catalogue from a new test account you create just for this test. This can help rule out user-specific issues. Often things can be solved just by moving the preferences out of the way and starting from scratch. Using a test account is the best way of isolating these sorts of common app problems.

- Check your video driver, and then check them again. Lr is usually pretty forgiving of driver issues, and does not have a specific dependency on GPU functions, but it drives the 2D viewports pretty hard via standard API calls. If one or more of those API calls is a problem, then you will see exactly what you describe here.

- Check the other threads for how to purge the ACR cache, setup previews appropriately, and, if necessary, recreate the previews from scratch. A large number of the people who saw problems going immediately from Lr 3 to Lr 4 solved them with these few small steps.