Very Bad Performance of LR 4.1 on High Spec Systems

  • 1
  • Problem
  • Updated 6 years ago
Dear Adobe Team

I'm a proud User of Adobe Lightroom 3.7 and am currently testing Lightroom 4.1. I'm very happy with the general performance of Lightroom 3, but not with the one of Lightroom 4.1.

There are several serious Issues, which make LR 4 unusable. While i enjoy the new Process Version of LR 4, it's Performance is very bad and can almost described as unusable!

Here are my System specifications, so my System is certainly not the cause of the painfully slow performance of LR 4.1:

OS: Windows 7 Ultimate Edition x64
Processor: Core i7 3930 @ 4.6 GHz
RAM: 32GB
RAM used by LR 4: ~3GB
HDDs: RAID 10 with a Adaptec 6405 Raid Controller and 4 Caviar Black 1TB Plates
OS is on a separate SDD

The LR 4.1 Catalog includes 4000 Images. In LR 3 my Catalog includes about 50'000 Images and it's pretty fast and reliablel.

My Issues are as following:

Library:
- Rendering of 1:1 Previews takes around 7-12s per Image (with this Machine there should be a much shorter Rendering Time. Processing a Batch of 200 Images in Photoshop takes about 2-4s per Image)
- Viewing a folder with about 200 Images takes ages until even Minimal Previews are correctly rendered
- Updating Metadata and Previews using "Synchronising" takes a very long Time (200 Images take over an hour)
- Exporting Images without rendering 1:1 Previews is faulty. Basically the Metadata is ignored if the Preview hasnt been rendered!
- Updating the Metadata (Loading and Saving) does not work properly. The Arrows indicating the Status of the Metadata (Metadata changed or not saved) don't represent the current status of the Metadata. (I save the Metadata, but the Arrows dont change)
- Synchronising over a Batch of 200 Images is faulty, some Images won't be Synchronised, which makes it neccessary to check and Recheck every single Image or even render 1:1 images.

Development:
- Very slow performance
- poor performance and response with all tools and options
- the Brush Tool has an extremely poor Performance
- Sharpening, Clarity and Noise Reduction do slow things down even further.

- other Modules
I don't need and I don't want them! They blow up the Programm and take away important resources, which might be much more usable in the Key-Areas of LR. The Library and the Develop-Module.

With those Bugs, Lighroom 4.1 is no option for me, I can't seriousely work with it, mainly because its poor performance and laggs. Until Adobe fixes these Issues, I won't buy LR 4.1.

Additionally, it's funny because Adobe Brides is able to render the Previews extremely fast.
Photo of BlackSwan

BlackSwan

  • 5 Posts
  • 0 Reply Likes

Posted 6 years ago

  • 1
Photo of jdv

jdv, Champion

  • 728 Posts
  • 56 Reply Likes
If you don't click on those other modules to open them up the first time, then they are not loaded and they take little, if any, resources. Just don't click on them, or right-click on the module bar and disable them if you never want to see them.

There is a very long thread about develop performance that has a lot of advice. Have you reviewed it?
Photo of BlackSwan

BlackSwan

  • 5 Posts
  • 0 Reply Likes
I've read all those Topics, and tried the multitude of advices.
None of them work.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 382 Reply Likes
Yep, you are being bit by a bug or 3, alright. Adobe is "no-doubt" working on a fix for 4.2. In the mean time, you may (or may not) be able to find relief by deleting wonky files and removing problem hardware or updating (or down-dating) drivers, etc... See the multitude of threads about it on this and U2U forum.

PS - As John said, unloaded modules take no resources...
Photo of Steve Sprengel

Steve Sprengel, Champion

  • 2643 Posts
  • 337 Reply Likes
If LR was horrendously slow on my new, fast computer system I'd have these questions:
Is LR using an inordinate amount of CPU or perhaps hardly any at all in Develop?
Is LR using only one thread instead of many most of the time?
Does LR 32-bit work better or worse than LR 64-bit?
Does LR work better if I install the newest or maybe last-year's video driver?
Does LR work any better or worse if I set my GPU-acceleration to Performance vs Quality?
Does LR work better if I move the LR3 preferences file somewhere else, temporarily?
Does all of my RAM run fast and without errors?
Does changing the size and location of the system page-file make any difference?
Does changing the drive for the system and user TEMP folders make any difference?
Is LR getting I/O errors or showing seconds-long slowness in each I/O done against the SSD vs the RAID vs a separate USB-attached drive that holds the catalog and photos? I'd use ProcMon from www.SysInternals.com to check this, filtering on the LR process and set it to discard filtered (hidden) data so as not to fill up my memory too fast.
Does LR work any different if I start a new catalog on a different drive from my current one and only import a handful of photo?
Does LR work any different if I install it to a different drive than it current is on?
Photo of Steve Sprengel

Steve Sprengel, Champion

  • 2643 Posts
  • 337 Reply Likes
I think you miss the point of most of these "questions I'd try to answer". They are to determine what machine or software subsystem on your computer LR4 has the problem with, not to find fault outside of LR4. LR4 certainly has a bad problem or three when run on some computers, so I would suggest not to ignore some of the questions just because you don't want to run your system that way permanently or feel it shouldn't matter.

In reviewing your answers, I'd still suggest trying the following, for diagnostic purposes--maybe Adobe has not figured out what is wrong and your answers will help them, not necessarily how you want to run your computer on a continuous basis, obviously:

Install and run the 32-bit LR4 to see if it works better.

Run things with your LR catalog and photo location on a USB drive or an "regular" SATA drive or something that is not the SSD and not your RAID system--LR3 has had problem even moving files properly when there is a RAID system involved.

I can't quite tell if you tried this, but if not, temporarily remove the LR3 preferences file from the common folder where both LR3 and LR4 use their preferences file from. Although it doesn't really make sense, this specific thing fixed performance issues on at least one system.

SysInternals' ProcMon will show I/O timing and if any of the system-calls had an error which were retried via another I/O method. This is not to look for disk errors which you shouldn't have any, it is to look for I/O being done multiple times or I/O that takes much longer than it should.

Try completely different video driver vintages and GPU performance settings. Despite LR4 not using the GPU for low-level RAW conversions, it is clearly using the video-card features to display things and even back in LR2 days fiddling with the performance settings would make LR2 work well or badly. I saw someone here saying that they had to roll back their video-card drivers 2 minor version levels (which would have been months apart in release time) to get LR to work well. It may be that some function in the video-driver is implemented poorly and only LR4 is utilizing that function, so all other software works well.

Please enable virtual memory on your system--with the paging file on your RAID volume to keep the SSD writes to a minimum. Try both the 64-bit and 32-bit versions of LR with VM enabled. It could be that LR assumes virtual memory in some of its caching schemes and a system call is repeatedly failing and the failure is being ignored or worked around in some very inefficient manner. It could also be that LR4 is taking a ratio of RAM to VM somewhere to decide what to do and with 0 as the VM size, LR4 is making a poor choice.

Just because all other programs including LR3 work fine on your system doesn't mean that LR4 has some quirky thing it is trying to do to optimize performance that your system isn't handling well and is resulting in a big problem for it. LR4 does require a newer version of the OS so they re-engineered how some things work compared to LR3 and it could be one of those things that LR4 does that your hardware/software environment isn't supporting well.

It is almost like your system is so fast that LR is continuously doing something wrong. This could happen if there is a multi-threaded bug where two operations are started and run in parallel with one against memory and one is against the disk subsystem, but there is really is a sequential dependence on the two things, and as long as the disk-based function finishes after the memory-based function things are ok, but if the disk one finishes first then the bug is seen. Maybe disk and memory are the wrong things to compare but you see what I mean.

The one clue that LR4 is confused or something is corrupted is that the LR4 catalog is extraordinarily large. I have a LR4 catalog with 25,000 images in it and the size is only 705MB. Does every version of your catalog that you have created in each location have this large size increase? If you have just moved your catalog from one location to the other then your catalog could be corrupted and causing all the problems. It also might be that one of the other factors is doing the corruption so creating a new catalog after every change, would be the only way to determine that.
Photo of Steve Sprengel

Steve Sprengel, Champion

  • 2643 Posts
  • 337 Reply Likes
I might add that in addition to trying different video-driver versions, if you have another, older video card, especially if it is the opposite major manufacturer (ATI vs nVidia) than your current one, swap video cards. LR4 may not have a bug but it may be using a video driver function that no other program is, so the slowness or bug only manifests when LR4 is running.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 382 Reply Likes
Steve, some good suggestions - not only the specifics, but the description of purpose, and how the logic of "my other programs aren't having problems with xyz, so xyz is not the problem.." can be a fallacy. Sometimes the devil is in the details, and only a particular program is exercising some detail. I recently tried a new graphics driver hoping it would solve a minor problem with Lr4 - it did, but then another program no longer worked correctly, so I had to downgrade. I've had to play "musical graphics cards" more than once in my computer life...

Ram with a stuck zero bit is only a problem when a program needs it to be a one. - say no mo'?
Photo of BlackSwan

BlackSwan

  • 5 Posts
  • 0 Reply Likes
@Steve

So what should i look for when i've filtered it only for Lightroom. ProcMon seems a bit confusing, not to say cryptic. Tell me, where would I be able to see I/O Performance or anything else except what registry entry it is reading from?

RessourceMonitor seems to be the better choise if you ask me.
Photo of Steve Sprengel

Steve Sprengel, Champion

  • 2643 Posts
  • 337 Reply Likes
I have plenty of File or Device Create/Open/Read/Write/Close, etc, operations listed in ProcMon, with the success or failure of each listed in the Result column.

Go look in Filter / Filters... and uncheck alot of the Excluded events. Those are more useful to exclude if you are capturing traffic from all processes and millions of things are being logged each minute.

I have over 200,000 events logged for the LR process after 5 minutes from opening LR up on my main catalog but not touching it after that.