Lightroom 3.3 Performance Feedback

I'm still having tremendous slow down issues while in Library mode.  It always happens after importing - AFTER it has finished generating previews.  LR 3.2 did not have this sluggishness.

Background info: I''m using the Canon 5D Mark II.  YES the images are huge.  I'm often importing 500-600 at a time.  I always let the previews finish generating before I try to do anything with Lightroom.  The images are on an internal SATA hard drive.  The catalog is on a separate internal SATA drive. 

Last night I imported my images.  And as I began working my way through the library to rate the images ... the delay between images was huge (hitting the left and right arrow keys to move between images).  It was often SEVERAL SECONDS between images which makes it hard to flip back and forth to compare  and adjust ratings.  (something I never had a problem with using LR 3.2 or LR 2.x or LR 1.x for that matter - I've been with you from the beginning)

Just to be sure previews were built, I selected all images in library mode and then told LR3.3 to regenerate the previews.  It quickly scanned all of the images - apparently determined that none of them had to be rebuilt (since it had just finished the import process) and finished the scan in mere seconds without having done anything.

I gave up and exited LR3.3 thinking I'd come back later and do the work.

But then on a whim, I decided to re-launch LR3.3 and see if anything changed.  And indeed, it appeared to be much faster moving between images after closing and re-opening the application.  Weird.

Anyway, please add the above to the data points in determining the performance issues.  I'll probably try the exit/restart strategy again on my next photo shoot.

Hi

Apologies if I am putting this in the wrong place.

I have just upgraded to 3.3 on a PC running XP.  I find that in the print module when I want to select another icc, when I select "other" nothing happens until I press escape when the program returns to the last profile used.

Any help would be appreciated

Sean

Tom Hogarty wrote: Please use this discussion topic for your feedback on Lightroom 3.3 RC and the final Lightroom 3.3 release when it becomes available.  The Lightroom team has tried very hard to extract useful feedback from the following discussion topic but due to the length and amount of chatter we need to start a new, more focused thread.  Please post specifics about your experience and be sure to include information about your hardware configuration. Regards, Tom Hogarty Lightroom Product Manager

Tom,

I'm not 100% sure this thread hasn't digressed in some areas, as did the other discussion thread, but it does seem folks have tried to bring some technical clarity to their posts.  Since you started this new thread though, I think it would extremely helpful to all of us (and encouraging) if yourself or someone like Dan T. etc., could provide some regular update on areas where Adobe thinks they may have a lead or handle on certain performance issues. It's tough when you're having one of these issues to only hear the voice going only one way.

I truly believe that the makeup of most of the folks on this forum are those that truly want to make LR better and have a very vested interest in its success.  That said, having more of a two way dialog between the community and Adobe I think would be a great asset to both sides.  I know the team is probably very busy working on this and future items, but having someone as a communications link would be very beneficial I believe.

Thanks in advance...

Jay S.

Hi,

IMHO, the following question should be added to the Lightroom bug report form (or should be asked when users are reporting problems with LR):

If you have upgraded from a previous version, did you uninstall the previous version before installing the new one?

It would be interesting to see if there's a relationship between the way LR has been installed (upgraded) and the fact that a given user is hit by these performance problems. If there's an obvious correlation, we might have discovered something interesting.

I recently got in touch with someone who has access to the test versions of LR and he told me that Adobe always recommend to uninstall the previous version before installing the new one. If I remember well, the installer doesn't make such a recommendation. If this is necessary the installer should proceed by itself with the full uninstallation of the previous version before installing the new one (at least, if it has the same major version number).

My two cents...

--

Patrick

Tom/George/Agnus1 & Others,

Warning: This is a long post.

I may have found a workaround for the problem I have been having with system lags and hangs, particularly during the use of the spot healing tool.  It is a little early to tell but I am optimistic.

After watching the CPU meter during periods where LR would hang after adding a new spot or modifying the size of the existing spot from the spot healing tool, I kept noticing that during the hang time one of the 16 cores would be at 100% and the other were fairly much not operating at all.  When the hang would break, all the CPUs would then become partially and randomly utilized.  Very strange.

After some internet searching I found out about a program called the Windows Event Viewer (type Event Viewer in the start menu).  From this lead, I found the Windows Event Viewer was recording massive"information" entries with "amdkmdag" listed as the source,"62464" as the Event ID and "DVD_OV" as the Task Category.  The number of entries was easily hundreds a day and many times 20-100 in a single second, and the second I was looking at was when LR was hung up with the spot removal tool.

A little more research of this "amdkmdag" service lead me to finding it was called the "ATI External Event Utility" and given its name, probably related to the ATI graphics card I have installed.

After digging deeper into what overhead runs in background on account of the graphics card software and drivers, I decided on a hunch to disable all that I felt was of little current value, but especially the ATI External Event Utility.  So I did two things:

1.   Disable ATI External Event Utility.  This was accomplished in the registry as follows:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Atierecord]

"eRecordEnable"=dword:00000000

I learned how to do this from a discussion at:  http://209.147.121.98/board/showthread.php?t=33960196&mode=linear

2.   Remove unimportant (to me) graphics card services (5 total) from start-up:

CCC.Exe,Atiedxx.exe, Atiesrxx.exe, Mom.exe and LIStart.exe

I learned how to do this from a discussion at:  http://www.ghacks.net/2010/01/07/what-are-ccc-exe-atiedxx-exe-atiesrxx-exe-mom-exe-and-clistart-exe/

The result is that my performance in the Develop module is much more as I expected when upgrading (slightly slower than 2.5 but still pretty zippy given the horsepower in my system).  In particular, I am now rarely getting a hang up with the spot healing tool and if I do it is only for a couple of seconds.  Back in business!

I probably didn't need to do both steps as they both probably disable the event messaging but I don't want to figure that out right now since my system is again functional and I really don't want to go backwards at this point.

This might help some of you out there with ATI cards running Windows 7.  I will be real disappointed if my problem returns down the road, but not completely surprised.  If George and Agnus1 could give this a try that might confirm if the workaround is useful for systems with similar hardware.  This may only be a problem with W7/ATI systems or it may exist in other combinations but less noticeable.

As a closing note, I have had to disable an administrative service utility as a workaround to my system lag problem.  That does not mean it solved the problem itself and I will of course share this with my bug reporting contact at Adobe as well so they can look into the functionality of this service utility relative to version 2.5 where it didn't appear to be causing any issues at all.

Best of luck to all.

Jeff

After being very hesitant to go to 3.3 from 3.2, which worked reasonably well (though much slower than LR 2 series) except for the problem with watermarks that would suddenly stop working for some fonts, I changed when the RC was removed.

With no changes to my system except for the change to 3.3 I have began having problems with speed and with hanging. Generally, this is in the developement mode where I notice it most. Today, while checking presets on some photos it began hanging when I did nothing execpt run my mouse over the presets to look at the small preview screen. It would run my processor up to 100% just the show the miniscule preview! Usually I have to actually apply the preview to really tell anything, but it bogged down to the extent it took 10 or more seconds to apply or remove the preset from the file.

I optimized the catolog, which has always been akin to rebuilding permissions on a Mac---something to do to keep one from throwing the machine out the window until you calm down, but fixing nothing---with no change. I restarted LR a number of times. No change. Deleted cache. Naturally, no change. Rebuilt premissions and restarted just for grins and giggles. No change.

The improved processing, sharpening, and noise reduction are nice, but frankly the continued problems with LR 3 make it not worth the trouble, especially when I can get equal image quality and fewer headaches with other RAW processors.

iMac 10.5.8, 8gb etc. Should make no difference since it worked with 3.2....

The below example of my spot removal on a raw image runs excruciatingly slow.  There is an enormous page fault rate during this slowness, all the while memory and processor are going unused.  Anyone can duplicate this problem by slapping about that many dust spots against any uncropped raw image.    Fix this situation, and I will bet the same solution fixes a lot of other problems as well. Thats just my educated hunch.

Hi,

Tom Hogarty wrote: Please use this discussion topic for your feedback on Lightroom 3.3 RC and the final Lightroom 3.3 release when it becomes available.  The Lightroom team has tried very hard to extract useful feedback from the following discussion topic but due to the length and amount of chatter we need to start a new, more focused thread.  Please post specifics about your experience and be sure to include information about your hardware configuration.

So I'm moving to this thread excerpts of reports that I have made in other threads.

I have no performance problems in the Library module. I only have problems when using the local adjustment tools.

I'm running LR 3.3 under XP Pro SP3 32-bit (3GB - fast hard disks with a lot of free space). Dual monitor. Processor: AMB Athlon 64 X2 Dual 2.21 Ghz. NVidia GeForce 9500 GT. Lastest driver installed. NView disabled.

Thanks in advance for your efforts.

Prior to upgrading computer during the 2.x era, LR was sluggish in rendering and brushes and gradients were all but unusable.

With my current spec below, I render in about 1.5 sec. The brush, gradient and spot tools respond extremely smoothly regardless of mutiple uses.

Never a slowdow, never a crash.

Photos on system drive, lrcat on system drive, cache on second drive. Cache - 50 GB

System drive is 2X 1TB 7200 Seagates -  RAID 1. Second Drive is 1 TB 7200 Seagate

Graphics card is NVIDIA GTX 275 w/896MB VRAM

Lightroom version: 3.3 [711369]
Operating system: Windows 7 Business Edition
Version: 6.1 [7600]
Application architecture: x64
System architecture: x64
Physical processor count: 8
Processor speed: 3.5 GHz - (2.6 GHz Core i7 920 OC'd to 3.5 GHz)
Built-in memory: 12279.0 MB
Real memory available to Lightroom: 12279.0 MB
Real memory used by Lightroom: 194.2 MB (1.5%)
Virtual memory used by Lightroom: 206.3 MB
Memory cache size: 79.8 MB
System DPI setting: 96 DPI
Desktop composition enabled: No
Displays: 1) 1680x1050
Application folder: C:\Program Files\Adobe\Adobe Photoshop Lightroom 3.3
Library Path: C:\Users\DAD\Pictures\Lightroom\RR.lrcat
Settings Folder: C:\Users\DAD\AppData\Roaming\Adobe\Lightroom

Please, please, please fix the problems with the adjustment brush and the spot healing tool. Why has a problem this serious, which makes Lightroom virtually unusable, been allowed to persist over multiple versions? A problem this serious should be at the top of the TODO list. I've had to stop using Lightroom for the immediate future because of this ongoing problem.