LR 6.7 on a fairly fast setup is still very slow....

[Phil Indeblanc]

I admit I may have overlooked an optimal Preferences setup to make it as best as can be, but, here is what I have....

All pretty high, if not very high spec gear:
3.6Ghz 6 core intel
32gb ram
SSD 500gb
SSD 64gb PS swap drive
SSD (was enabled to use as Page File, but I stopped)
I keep my drives 50% empty.
Intel server to store my images. They are at a sustained 40-80 at best mbs transfer speeds.
My files are mostly 22mpixel, and 42mpixel raw files.
GTX 970, i think has 4gb of memory
30" inch screens, but I don't even bother with Dual screen with such poor speed.
------
The Sys info says:
Lightroom version: 6.7 [ 1090788 ]
License: Perpetual
Operating system: Windows 10
Version: 10.0
Application architecture: x64
System architecture: x64
Logical processor count: 12
Processor speed: 3.3 GHz
Built-in memory: 32678.9 MB
Real memory available to Lightroom: 32678.9 MB
Real memory used by Lightroom: 6917.3 MB (21.1%)
Virtual memory used by Lightroom: 10509.3 MB
Memory cache size: 6974.2 MB
Maximum thread count used by Camera Raw: 12
Camera Raw SIMD optimization: SSE2,AVX,AVX2
System DPI setting: 96 DPI
Desktop composition enabled: Yes
Displays: 1) 2560x1440, 2) 2560x1600


Graphics Processor Info:
GeForce GTX 970/PCIe/SSE2

Check OpenGL support: Passed
Vendor: NVIDIA Corporation
Version: 3.3.0 NVIDIA 369.09
Renderer: GeForce GTX 970/PCIe/SSE2
LanguageVersion: 3.30 NVIDIA via Cg compiler


Application folder: C:\Program Files\Adobe\Adobe Lightroom
Library Path: C:\Users\*\Pictures\Lightroom\LRcatalog-2.lrcat
Settings Folder: C:\Users\*\AppData\Roaming\Adobe\Lightroom

Installed Plugins:
1) Canon Tether Plugin
2) Facebook
3) Flickr
4) Leica Tether Plugin
5) Nikon Tether Plugin
Config.lua flags: None

Adapter #1: Vendor : 10de
   Device : 13c2
   Subsystem : 29783842
   Revision : a1
   Video Memory : 4058
Adapter #2: Vendor : 1414
   Device : 8c
   Subsystem : 0
   Revision : 0
   Video Memory : 0


I have "Use graphics processor" enabled.
I have not checked or created smart previews for editing yet. I would want to avoid this until I really have to.

What else can I do?
I am starting to look for alternate apps. I have C1, and I also own a number of Digital Asset management apps, but I WAS enjoying LR's simple 1 interface appraoch. I was dealing with the locked in tools, but with the past OK speed, it was slower, but useable.
Now, I make a change the screen goes black for a second to display, then shows up, its just a mess. Its gotten to the point that I click on a thumbnail to highlight and preview, I move the mouse over without waiting, to another thumbnail, and that second thumbnail the mouse is only hovering over ends up in the preview!

Your thoughts?

[RikkFlohr]

What is slow?

Using an Adjustment Brush? Sliding the Tint slider? Walking from one image to another in Develop? Library Loupe? Exporting 50 images?

Without exact mentions of what precisely is slow and how long it takes in seconds, it is difficult to discern if:

1. Do you have typical behavior?
2. Is it a system-specific issue?
3. Is it a Lightroom issue?

For example, GPU speeds up Develop Slider performance but slows the walking between images.  d

Knowing what is your pain point and quantitatively how long something takes will help diagnose.

[Cem]

The bottleneck here might be the read/write speed of the Inter server for images. Try copying some images to one of the SSD's and import into LR. See if the performance improves.

[uimike]

Rikk,

Thanks for being here. I too have noticed a sizeable slowing down after the last update. I could post all relevant info if needed, but basically its a MBP Retina '14, with GT750 and Intel graphic processing, catalog and previews on an external 1T SSD.

When developing, using the gradient filter, clone/heal, brush cause the Activity Monitor show energy use to spike to 400, 500%, stay there for a while. The mac's fan turns on and stays on for maybe 10-15 seconds.

That didn't happen before, and I am sure all things are equal.

I tired a bunch of things, not sure if anything made it better.

In addition, previewing got slower, and, especially, 1:1 zoom got very very slow.

I tried using smaller previews, lower res, etc, and ultimately decided to select a few thousand files I'll be working on and do the Library > Preview > Render 1:1, and keep forever.

Took a while but now previewing is faster.

The developing tools I mentioned above got marginally faster, enough that I don't get too annoyed - but I am almost feeling like getting a new Mac, with its faster processor/cores. 

just my 2 cents,

/mike

[CeeVee]

You are storing you images remote (to you) on a server and surprised that your taking a speed hit?
Neither LightRoom, Photoshop or (ugh) Bridge is optimized to do that. Why are you surprised?
If you are bringing your images to one of the SSDs and operating on them there and see a speed hit caused by the last iteration/update than something has indeed gone into the dumper. Time to run checkdisk as a starter.

Sent from my SAMSUNG-SM-N900A using Tapatalk

[Phil Indeblanc]

What is slow?

Using an Adjustment Brush? Sliding the Tint slider? Walking from one image to another in Develop? Library Loupe? Exporting 50 images?

Without exact mentions of what precisely is slow and how long it takes in seconds, it is difficult to discern if:

1. Do you have typical behavior?
2. Is it a system-specific issue?
3. Is it a Lightroom issue?
For example, GPU speeds up Develop Slider performance but slows the walking between images.  d
Knowing what is your pain point and quantitatively how long something takes will help diagnose.

Good questions!

I just disabled the graphics card and noticed a big improvement of workable difference!

So, yes as I pointed out, it was mainly the navigation having issues.
Although the adjustment brush is slow, and does behave like it needs to catch up to my actions and therefore doing adjustments or movements in places I don't want, but, I am dealing with it for the moment.

You are storing you images remote (to you) on a server and surprised that your taking a speed hit?
Neither LightRoom, Photoshop or (ugh) Bridge is optimized to do that. Why are you surprised?
If you are bringing your images to one of the SSDs and operating on them there and see a speed hit caused by the last iteration/update than something has indeed gone into the dumper. Time to run checkdisk as a starter.

Yes, I have been storing images on a server for about 10 years now and I have been updating hardware pretty regularly.

I am surprised as I have been dealing with images for the past 25 to 30 years, and it is *again recently that I have noticed LR behaving very slow. It once or twice did this in the past versions with updates making some improvements, at least to be acceptable to a degree. Now it is not.

I have 8TB of image data across 3 servers, and another set in a JBOD drive setup. And while I had multiple catalogues, I was suggested that the size would make no difference, so I have also recently started to merge at least a "master" catalogue to try this out. Still have the others.


I can answer specific questions in hopes to help me and others.

[uimike]

CeeVee,

SSD is about 6 months old. I did run Apple's DU as well as DiskWarrior and both said disk was OK.  Any thoughs?
I did think about the external SSD, but the internal is an SSD too - except Apple-supplied. Could something be happening to the non-Apple one?

mike

[Phil Indeblanc]

Ya, while it changed the behavior a bit, and did feel faster to change thumbs selected, its just slow as syrup.

I cannot continue like this, but I do want to investigate my options before I do anything drastic.

[uimike]

Phil, are you getting high energy counts, fan?

mike

[Paul2660]

LR at least on the windows side seems to benefit 0 amount from enabling open CL.  As you have discovered, it may actually make things worse.

I have the same graphics card and I don't store off line to a remote server however.  All work done on a local series of drives.

Performance is slow, as before once you end up with a lot of local adjustments or attempt to zoom to 100%, the time taken to view the image slowly gets longer and longer.

You might try clearing the LR cache, as sometimes that will help, but once the real bog hits, best solution is a re-boot for me. 

Time it takes to load a 36MP image is just way to long, (by load I mean zoom to 100%) etc. 

Paul Caldwell

[uimike]

apologies for butting in, mac here...
Phil's card is much more powerful than mine, so Win does not benefit at all? wow.

[Paul2660]

LR seems to gain basically very little performance from a GPU, where as Photoshop, gains a lot.  Areas I seen massive improvement again are zooming, drawing, masking, scrolling around a image at 100%.  I use the Asus Nvidia GTX970 cards, and use their app to measure performance.  You can clearly see the card being used (both memory and processor) when utilizing advanced features in Photoshop, where as when using LR the memory and processor of the card do not budge, but instead watch your core processors, (i7) all 8 cores will be utilized and the system ram usage will also be peaked.  For LR, this is during any export, but also pano creation, HDR work, drawing local adjustments, etc. 

The code has been needing a total re-write IMO for years, but Adobe seems to treat it like many other things, one pass and move on.  Most unfortunate situation as LR is core piece of my workflow.

These are all files from 36MP to 100MP cameras. 

LR will tend to give you the spinning wheel, (lower right corner on the main screen)on a zoom to 100%, does not seem to like 30" monitors (something that has been a problem for a long time now), and I guess will be even worse on a 27" 5K or 4K display. 

Paul Caldwell

[Phil Indeblanc]

I thought I was alone, and I do admit that the file size I now use are bigger, but this is while in 22mpixel Canon 5Dm2-3, it was still slow yet border line. And now I have the 42mpixel files, and its a new level of NOT USABLE!

Paul, thanks for concurring, as I am someone who does a lot of self refelcting before I get on here and ask questions. My core at one time was a Sys Analyst L2 specialist, and while some things are updated since XP, the mechanics have not changed all that much. I am running of course a 64bit... Win 10 system. Although I am not an expert by any means in memory usage of the OS to using page file and virtual memry in conjunction of video memory for Win10/64bit. Just never dissected that. This was a clean install too, less than a year! I did a fresh one thinking its time, as I know how things can accumulate. I have FireFox open with 3 tabs, my mail app, and now I am closing PS after I do a little cleaning on an image to free up anything.  I also tend to do any spot removal in PS, as I know that its one of the higher mem taxing bits of info LR does.


Mike, How can I check for high energy counts? Not sure I follow :-(

Also to address, these are new files I moved off the card, so they are not loaded with any preset or processing information to read and apply.

However, I am going from Lib mode to Dev mode or Eval mode...Just overall like walking through tar pits.

I posted my sys info, and if there is ANY test I can do for y'all to see whats up, I am more than happy to do so.

[Paul2660]

Hi Phil,

I have an IS background also, not as specialized, but years in the field.  All windows based equipment, (however I see a lot of this on the mac also)

LR is a great tool, but Adobe is just not very focused on problems.  And many times, they seem to drop in a toolset or feature and that's it.  Performance has been a issue for me since about 1 year ago.  I totally rebuilt a new machine i7 4Ghz, 32GB of ram, all SSD for OS and LR, with the same Graphics card, and the issues are the same.  LR's real use of open CL, is nominal at best and needs a total re-write.

In a way, it's just like the Adobe pano tool, great tool but fraught with problems on exposure.  Consistently will blow out close highlights, to worthless.  Same series of files in Adobe CC no problems, but Adobe CC does not have the boundary warp, which is a great asset for me.  It's been this way from day one and like many issues in LR, it seems Adobe made their one pass and done.

Paul Caldwell

[rdonson]

https://helpx.adobe.com/lightroom/kb/optimize-performance-lightroom.html

Performance hints from Adobe but true to their nature no date as to when this was written although their reference to Windows 8 might be a clue.

https://helpx.adobe.com/lightroom/kb/performance-hints.html

Perhaps more recent and down to earth advice.

http://www.lightroomqueen.com/lightroom-performance-workflow-tweaks/

[Phil Indeblanc]

Thanks for the thoughtful feedbacks. Much appreciated. Really frustrating with the number of variables involved and to pinpoint.

At least its not my system :-/

So whats the next step? Put C1 back into action as I had a few years back before LR3 conversion?

This is kind of telling my self "you were right" when I kept preaching NOT to commit your files to one system of a database. Use a DAM and stick to that. I think its probably in the DAM category when it started.
I own:

1. ACDSEE, a great image browser (that doesn't support IIQ /Phasei One files, so I cant use it solely).
2. Bibble
3. BreezeBrowser
4. Extensis Portfolio
5. Fast RawViewer
6. FastStone
7. ID Imager
8. iMatch
9. MediaPro/PhaseOne
10. PhotoMechanic
11. Zoner
12. ...Probably a couple more I need to look through to find...Like Corels Raw processor. It had buggy issues, so it was out the first day. Usually Corel has "solid" / innovative products. Maybe they improved?

I like C1 although hate the shift from a standard Win OS placement of tools and such, but I think I can convert. But I don't like that it has to create a folder structure IN EVERY FOLDER I have images in. That is a DISASTER for me, as I use higher Archy file management, which is the ONLY THING that could SAVE ME from this LR issue.

I love ACDSEE, I have the manager and Ultimate. Though the processing is a bit choppy, and fine tuning is hard, its actually a decent processor. But not for high level fine tuning.
I also liked MediaPro, but had issues with TIFF or large files, I might have to try it again as it has been some time.

ID Imager which I think is the same as PhotoSupreme, which I have both licenses, is really nice, but there are SO many options, there is a bit of a learning/adaptation curve...and when working, its hard to get things done, AND I don't know about the future support of it.
iMatch is the same I believe, or?

Fast Stone or Viewer, I think simply don't support all file types, but, I remember they had limits ACDSee surpassed.