Skip to main content
D
Dimizu
Known Participant
September 22, 2016

P: Slow performance on Xeon CPUs

  • September 22, 2016
  • 234 replies
  • 9082 views

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 has been closed for replies.

    234 replies

    Show previous replies
    B
    bob frost
    Inspiring
    May 3, 2017

    Hi Simon,

    I tried your config.lua a while ago and found no difference in the slowdown in rendering with time, BUT have now realised I had it in the wrong LR folder!!! Copying the .51 config.lua to the correct folder seems to have cured the slowdown in rendering D810 nefs. Early days, but I have just rendered about 1200 nefs without any slowdown!

    I haven't tried the config.lua with 0.5 but will do later.

    Some months ago, I had a look at what LR is doing during rendering with MS Process Monitor (filtered on lightroom.exe). I could see that when rendering became slow after an hour or more, it seemed to be spending more time creating and closing threads without anything happening (the RH side of the data lines were full of zero times). Is that the logjam; too many threads being created which can't get onto the 'motorway' and thus wasting LR time? Just had a look again at it running with 0.51 after 1200 renders and there seem to be far fewer threads being created and closed than before. I'm not a programmer, but this did seem to be a clue to me.

    I'll let this rendering continue for another hour or so, and then try the other setting, but you might, just might, have solved my slowdown problem. Never had a slowdown with editing, but then I don't sit editing for hours - it's my hobby, not work 😉

    Bob Frost

    Jerry Syder
    Jerry Syder
    Inspiring
    May 3, 2017
    Haha! I know the feeling buddy. If only it continued working as when we first launched the program. I think they are working on something to nail this issue finally so fingers crossed. 
    Assaf Frank
    Assaf Frank
    Participating Frequently
    May 3, 2017
    No worries mate, I have also started using smart previews and it makes a big difference, but it is not ideal when you need to check focus and zoom in, but it is defiantly more responsive.

    The main issue I want adobe to concentrate is the performance degradation.

    after restart everything is always much faster (without smart previews) and also creating panoramas are half the time if not less.
    my Config.lua flags is the same: 
    Develop.AdjustMaximumThreadCount = 0.51

    which I think makes a some difference in performance.
    but hey fix the performance degradation...

    we had enough restarting lightroom every time we want to speed up things.
    Jerry Syder
    Jerry Syder
    Inspiring
    May 3, 2017
    Oh dear!!! I may have been a bit hasty in my response ;-(!! Ashamed of myself, I stayed quiet until someone called me out. I guess when something appears too good to be true, they are in fact, too good to be true. Two things 1. I was using smart objects so this was not a fair test as I was not working on the full RAW file. 2. Things did degrade after about 10mins or so. n.b I switched off Smart Previews to see what it would be like - result, laggy but I must admit that after testing both cases(with or without smart previews) things are marginally better than before but nothing to jump and scream about. Also, in both cases, things did degrade after minutes of a LR restart.

    Config.lua flags:
    Develop.AdjustMaximumThreadCount = 0.51

    Lightroom version: CC 2015.10 [ 1111918 ]
    License: Creative Cloud
    Operating system: Windows 10
    Version: 10.0
    Application architecture: x64
    System architecture: x64
    Logical processor count: 8
    Processor speed: 3.4 GHz
    Built-in memory: 16325.8 MB

    Graphics Processor Info:
    GeForce GTX 1060 6GB

    ..............................

    Now I go bury my head 
    Assaf Frank
    Assaf Frank
    Participating Frequently
    May 3, 2017
    Hi Jerry,

    can you let me know the what is the line in the config.lua
    and do you notice any degradation in performance after a while
    and what is your spec (CPU/GPU/OS)

    Thank you in advance.
    Assaf
    Jerry Syder
    Jerry Syder
    Inspiring
    May 3, 2017
    Hey Simon, I would just like to pitch in here and say that I'm gobsmacked! I never even thought that Lightroom was capable of doing what I'm seeing it do now that I've taken the steps suggested. I'm actually trying to keep up with the speed(someone please pinch me now, I am dreaming right!?!). I may be counting chickens but so far I've just been going through image after image and doing my general edits for an event and it's all snappy with the config.lua doing it's thing. I was a bit adamant to give it a go because I, like some others here, didn't quite get what it would do(in fact, assumed that it would use less cores). After reading your metaphor of the traffic scenario, I thought ahhh lets try. Jerry happy 🙂
    F
    FeedbackCommunityMember
    Inspiring
    May 3, 2017
    Affinity has no point whatsoever. On my 6/12-core at least not. This is complete nonsense. 
    Lightroom uses all cores (all 12 logic cores) when exporting, creating 1:1 previews etc. While editing it uses for 1 core of power, maybe 2. I can set affinity to only 1 core and performance would not suffer mauch. But it would be huge difference on export. If U se GPU there is boost in performance regardless of number of cores. But for brush, I need to switch off GPU in settings. Which is annoying, and I do not do it always. Brushes doing ok under GPU, I just do not see what I'm, painting until I stop and area get overlay. For simple things I paint on "air". If I need to be precise, I turn GPU off. Annoying. SInce I use Lr only for "preset/auto" stff latelly I don't care anymoore. Adobe will lost one customer when my 1 year CC runs off. No point wasting my creative life here. 100's of replyes and no solution. It can't be...
    excorp11
    excorp11
    Inspiring
    May 3, 2017
    Simon,

    Very slight improvement, but nothing I'd label as significant:

    at .51 (copied from above) no mask  =     17       20     27      38 
    at .50                                  no mask  =     15       19     27      33

    I also tried to do some editing sessions this weekend, both with and without the patch and with various affinity masks.  Nothing keeps 2015.10 running smoothly for more than 5-10 images.  Limiting the cores is a definite improvement, but it still becomes unusable in very short order. 
    S
    Adobe Employee
    simonsaith
    Adobe Employee
    May 2, 2017
    Copy the config.lua file into User > AppData > Roaming > Adobe > Lightroom.

    Sorry for the late response. I just got back from a leave.
    S
    Adobe Employee
    simonsaith
    Adobe Employee
    May 2, 2017
    Thanks Mark for sharing the results of your experiments. Can you try tweak the config.lua in an editor and set the value of Develop.AdjustMaximumThreadCount to 0.5. So in Lr's system info, you should see

    Develop.AdjustMaximumThreadCount = 0.5

    and check the your experience without the affinity mask.
    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