5 Replies Latest reply: Jun 30, 2010 5:57 PM by TK2142 RSS

    LR3 "Develop Module" slowing related to noise removal

    KulorDS Community Member

      Hi all. As many fellow early adopters to the full release of Lightroom 3, I have been experiencing very slow rendering and response times when editing in the Develop module. I am on a very powerful machine that meets and exceeds the requirements by a long shot--quad core, 8 gigs ram, 64bit win7 and a solid state drive. There is absolutely no reason on my end that I should be experiencing any kind of slowing, especially when I would get a flawless experience in LR 2.x, and even the early LR3 betas.

       

      So I did some fiddling and I believe I may have pinned the slowing down to the adjustment brush, and even more so with the new noise removal. It appears the algorithm being used in the new noise removal tool is a system resource hog. I ran a few "tests" to see if the issue is in fact related to noise removal, and it seems so. When I have an image open at default settings, there is no visible render time--its instant. But when I add noise, I find the render time to jump exponentially. Every 10% increase on the slider adds about half of a second on the render time, and my CPU usage jumps, and likewise I see an increase in memory usage. The higher on the slider, the slower the render time and the more memory is being used.

       

      What I suggest for everyone experiencing the slow loading times is to entirely disable noise removal while editing, and see if it results in faster editing. If the noise removal IS the culprit, wait until you have edited all of your images in a set and then copy the noise removal onto each image in a batch as the very last step before exporting for print/web.

       

      Hope this helps others, as it truly did help me.
        • 1. Re: LR3 "Develop Module" slowing related to noise removal
          JayS In CT Community Member

          Kulor,

           

          It's been discussed in a number of the "slow" threads, amongst a number of other things.  Simpler way to test is to just turn the detail tab on and off and the difference is noticeable and immediate.  As someone else mentioned though, you can't go completely without seeing what effect your NR is going to have while editing.  Somewhat of a catch 22.  The new NR is great, but I think it may be one of the areas Adobe may have to look at as far as overall performance.  Comparitely with LR 2.7 there is a huge difference to the UI impact.

           

          Jay S.

          • 2. Re: LR3 "Develop Module" slowing related to noise removal
            TK2142 Community Member

            Thanks a lot for sharing. I've yet to confirm this myself but it could very well be the case that LR starts to behave like molasses as soon as I start using the "Details" tab.

             

            Often performance in the develop module is acceptable (not immediate as it should be on today's hardware, but acceptable) but after a while the lack of responsiveness becomes ridiculous. Previously, I assumed LR cannot handle a high number of brush strokes and/or edits in general. I'll have to monitor whether the slowing down is related to the use of the "Details" tab.

             

            I hope this forum hasn't turned to a self-support group. I don't see the usual professionals post anymore. Hopefully they are just all on a well-deserved break but will return in due course.

             

            It is frustrating to be left with bugs like the Flickr republishing bug and not even get an acknowledgement that it has been added to the list of things to fix.

            • 3. Re: LR3 "Develop Module" slowing related to noise removal
              JayS In CT Community Member

              TK2142 wrote:

               

              Thanks a lot for sharing. I've yet to confirm this myself but it could very well be the case that LR starts to behave like molasses as soon as I start using the "Details" tab.

               

              Often performance in the develop module is acceptable (not immediate as it should be on today's hardware, but acceptable) but after a while the lack of responsiveness becomes ridiculous. Previously, I assumed LR cannot handle a high number of brush strokes and/or edits in general. I'll have to monitor whether the slowing down is related to the use of the "Details" tab.

               

              I hope this forum hasn't turned to a self-support group. I don't see the usual professionals post anymore. Hopefully they are just all on a well-deserved break but will return in due course.

               

              It is frustrating to be left with bugs like the Flickr republishing bug and not even get an acknowledgement that it has been added to the list of things to fix.

              TK,

               

              No problem..  would be interested in what you find turning it on and off on your machine.  As for the Flickr issue, did you let Adobe know formally?  There are Adobe who are here, but since this is user to user, you can't always depend on them getting the word from here.  I wouldn't want to be on the end of trying to prioritize some of the issues that have to be looked at.  Having spent a fair number of years coding, you try to find that elusive "common" module that may be impacting a number of things.

               

              Jay S.

              • 4. Re: LR3 "Develop Module" slowing related to noise removal
                PIRose Community Member

                TK2142 wrote:

                 


                I hope this forum hasn't turned to a self-support group. I don't see the usual professionals post anymore. Hopefully they are just all on a well-deserved break but will return in due course.

                 

                But let's not forget (despite the fact that Adobe staff has helped here in the past--and hopefully will continue to do so) that this is a user-to-user forum. IOW, it is a self-support group. To cite Adobe's description (of these forums): "...where Adobe users exchange questions, offer ideas and suggestions, and share tips and tricks."

                 

                Phil

                • 5. Re: LR3 "Develop Module" slowing related to noise removal
                  TK2142 Community Member

                  JayS In CT wrote:

                   

                  No problem..  would be interested in what you find turning it on and off on your machine.

                  Sadly, turning it off doesn't help me. I haven't tried to not use it instead of using it and turning it off afterwards yet, but I suspect that won't make a difference either.

                   

                  I'm experiencing terrible lag with the adjustment brush on images where I have done lots of edits already. I create a stroke and 2 seconds afterwards it is actually drawn.

                   

                  Playing with your suggestion, I discovered that I can address the lag by reducing the image size. Either exiting "full screen" mode and making the program window rather small or by adding the film strip back to the Develop view, I can reduce the lag to the standard "not ideal since not immediate but acceptably fast" speed.

                   

                  I've read elsewhere that reducing the displayed image size addressed performance issues.

                  I haven't tried to use "1:1 previews" whether these may make the perfomance image display size independent.

                   

                  I hope this issue will be fixed in the future. It is so nice to be able to switch off the top and bottom panel (sometimes even the left side panel) in Develop mode. It would be bad to be forced to have them all in -- or even exist "full screen" mode -- just to address the performance issue.

                   

                  As for the Flickr issue, did you let Adobe know formally?

                  I have just submitted an official bug report.

                  During the BETA forum days that didn't seem to be necessary as Community Professionals would try to reproduce bugs and then forward them on to the programmers. They also confirmed that they did it. That was really nice.