Skip to main content
Dimizu
Known Participant
Sep 22, 2016 8:45 AM UTC
In Development

P: Slow performance on Xeon CPUs

I noticed that LR clone and brush tool on my XEON E5-1650 0 3.20GHz (Attention: E5-1650 0 and not E5-1650 v4) can not stress my CPU and after x minutes of working LR slow down, until I have to restart it.

Please see the full diskussion with the problem here: https://forums.adobe.com/thread/2210245 (test with different Lightroom versions, confrontation with a weak laptop, that works fine, tests wit other graphic grafic card, test with other bios settings etc. No results. Only restart LR or minor display resolution helps.)

Can anyone with an XEON E5-1650 0 3.2Ghz confirm this?

    This topic is closed to new replies. Start a new post to keep the conversation going.

    234 replies

    Show previous replies
    Todd Shaner
    Todd Shaner
    Legend
    Oct 7, 2016 6:15 PM UTC
    The problem with that article is that no "editing" benchmarks were tested, such as using the Adjustment Brush and Clone tool, etc. I'm sure if they did the issues reported here would have surfaced. The benchmarks do clearly indicate there's little to be gained going beyond 4-cores.
    Translate
    bob frost
    Inspiring
    Oct 7, 2016 4:56 PM UTC

    Here is an interesting article on Lightrooms performance with differing core number -

    https://www.pugetsystems.com/labs/articles/Adobe-Lightroom-CC-6-Multi-Core-Performance-649/

    Bob frost

    Translate
    sw0rnenemy
    Participating Frequently
    Oct 4, 2016 7:18 PM UTC
    Same here and I've recently upgraded to a 10 core machine with a 4K display. It is so slow processing after the first few images that I just gave up. I'm using C1 in the interim until there is some sort of fix out.
    Translate
    Arnie47
    Known Participant
    Oct 1, 2016 8:39 PM UTC
    Servus Dietmar,
    I'm using LR on an i7 6 core machine and after upgrading to a 4k display I'm experiencing similar massive performance problems.
    Translate
    Todd Shaner
    Todd Shaner
    Legend
    Sep 30, 2016 4:39 PM UTC
    Simon, what exactly does the config.lua file do? You also mention tweaking the numbers, but what do they mean and how should you change the values?

    AgGCCache.mainCacheFactor = 0.1
    AgNegativeCache.factorOfAddressSpace = 0.01
    Translate
    DimizuAuthor
    Known Participant
    Sep 30, 2016 12:03 PM UTC
    @129856 Chen

    a)
    Yes, I can "reclaim" the speed with restart of Lightroom

    b)
    Now I tested your suggestion with the config.lua file.
    Result: unfortunately no solution 😞
    Translate
    bob frost
    Inspiring
    Sep 29, 2016 7:12 PM UTC

    For my rendering slow-down, the only way to reclaim speed is to restart LR. Simply stopping rendering and letting LR settle down and then restarting rendering does not speed things up. I'll let Dietmar deal with the editing slow-down.


    Bob F

    Translate
    Adobe Employee
    simonsaith
    Adobe Employee
    Sep 29, 2016 5:38 PM UTC
    Our engineers are looking into this. Is your known method to "reclaim" some speed back is to restart Lightroom/ACR? 

    @17495102 For your Lightroom slow down issue, could you try the following

    1. Open Lightroom.
    2. Invoke Lightroom > Preferences... menu command
    3. When the Preferences dialog appears, select the Presets tab.
    4. Click on the button labeled “Show Lightroom Presets Folder...”
    5. Lightroom will reveal the root preset folder in the Finder/Explorer.
    6. Now goto http://adobe.ly/2cEF782 and download the config.lua file and copy it into the root preset folder (under "Lightroom") at step 5. The config.lua file will reconfigure some Lightroom RAM usages for caching. 
    7. Relaunch Lr and follow your normal routines to reproduce the issue to see if it improves. You can also try to tweak the numbers to see if it makes any difference.
    8. Remove or rename the config.lua from the root preset folder after the experiment (to restore to the original Lr 6.7 behavior). 
    Translate
    bob frost
    Inspiring
    Sep 29, 2016 5:01 PM UTC

    There seems to have been no change in this problem since my last thread on this subject in June 2015.

    Bob Frost

    Translate
    DimizuAuthor
    Known Participant
    Sep 29, 2016 1:10 PM UTC
    Attention: your tests are renderung, my tests are edits. It is not the same.

    Yes you are right. Has do do with edits!

    But why the PC goes slower and slower also when I step to another photo? And why the PC not return fast when the CPU utilization goes to zero? And why I can not reproduce the problem on my weak PC?

    I think the problem is more complex: has do do with edits, CPU number, resolution etc. In my opinion, a fundamental problem in the kernel programming...

    I hope in a revision of kernel programming of LR...
    Translate
    Show more replies
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices