What's bottle-necking my editing speed?

Would yah look at that! Yup, it's a Type B :P. Any ideas on how to make the Esata connection work out of the back of my RAID? A PCI card or something I can buy to get things to work properly. That would greatly speed up the drives at the very least for now.

Looking at M.2 and it looks like my MOBO can handle the fastest type on the market, so I'm going to look into this just as a small project to get a bit more speed out of it for now

CyberDyneSystems wrote in post #18038741
Agree on the M2, the problem is he won't be putting a massive archive of RAW files on it (not likely)
Unless he can replace his approx 12TB array with an M2!

One option is to import to the fastest SSD available, do all the edits there, then move them to the RAID array when the set/event/project is done. I do this but substitute NAS for local RAID. They are still editable off the NAS/RAID, but things will be as snappy as possible while doing the majority of the work.

From the specs on the Asus Z170 A motherboard
With x4 PCI Express 3.0/2.0 bandwidth, M.2 supports up to 32Gbit/s data-transfer speeds.

The RAID configuration may very well be the root of the problem, but the SATA interface to the SSD
is no match for the PCIE x4 M.2 interface.

110yd wrote in post #18038755
From the specs on the Asus Z170 A motherboard
With x4 PCI Express 3.0/2.0 bandwidth, M.2 supports up to 32Gbit/s data-transfer speeds.

The RAID configuration may very well be the root of the problem, but the SATA interface to the SSD
is no match for the PCIE x4 M.2 interface.

Which only applies if he gets an NVMe SSD. The more common M.2 boards are no faster than his current SSD.

I'm too lazy to double check if I mentioned it, but I carried everything onto my SSD for a test run and it was still a bit laggy and behind when pixel peeping and editing. I'd rather not wait at all when adjusting sliders and such :/

The M.2 drives in my price range are no faster than the SSD I already have, simply smaller and more convenient but not really worth it. I'm not looking to spend $400 on a larger PCIe SSD that's blazing fast, I could put that money towards a lens or towards a 4tb internal and such.

xarik wrote in post #18038766
The M.2 drives in my price range are no faster than the SSD I already have, simply smaller and more convenient but not really worth it. I'm not looking to spend $400 on a larger PCIe SSD that's blazing fast, I could put that money towards a lens or towards a 4tb internal and such.

True. The good news is that SSDs are constantly dropping in price. Just keep as much of your "hot" data as possible on the SSD you have.

Before going out and buying new hardware, I suggest doing a google on what you can do from the software side.

Think about companies that you can outsource editing to. All you provide is your lightroom catalog. And how big is the catalog? Not big at all. You should be able to edit using just he catalog (without the RAW files behind the scene). This should significantly speed up any zoom in/preview/apply edit operations.

One way to speed it up is to use smart previews. Have the lightroom catalog on your computer harddrive, keep the raw files on an external drive. When importing photos, render smart previews and select 1:1. Then disconnect external drive and you can edit away at lightning speed. All changes will be applied to the raw files when you reconnect the drive.

Drawback is you cannot stitch panoramas or select "edit in photoshop" with the smart previews

mike_d wrote in post #18038751
Sadly, this is all too true. It seem like no matter how much horsepower you throw at it, the UI remains laggy. LR6 will use the GPU (or is that nVidia only?) to accelerate certain functions.

I am no speed animal but I really want to know how much difference a GPU (Green or Red) will make on LR/PS applications AND what different tiers have with greater impact (970 vs 980 vs 980 Ti vs 1080 vs 1070)

Turn off GPU acceleration if you haven't yet. I've had 2 AMD cards (including an r9 280) and neither worked right with that feature.

Beyond that, idk, I think your issue is definitely software related though.

You might find some useful info here: https://www.youtube.co​m …tKAmJ_9c&featur​e=youtu.be

I'm using a 2008 macbook pro. To help move things along, I do minimal edits the first go-round when selecting keepers. Using the Sync command to make global edits, etc. After keepers have been selected, I make Smart Previews which are much smaller files. Then move the original file to an external drive to keep my hard drive as empty as possible. Final edits are done with Smart Previews which appear to be much faster than with the original file. Originals are automatically updated when external drive is connected.

Simply moving the catalogue/previews from the RAID to an internal (preferably SSD) should give you a significant speed boost. With LR it writes to the catalogue file every time you move a slider. Once you have imported your images, and LR has created your previews, LR only accesses the RAW files when you need to export the image. So having the image files themselves on the RAID system should not slow you down. So you really only need to move the .lrcat file, although I would also move the associated folder structure with all the previews as well. If you don't LR will happily rebuild the previews, but either you will have to tell LR to do the whole lot, and it could take a while, or take the hit and let LR build them as you go.

Alan

I agree with Jake. There are a number of things a good machine will speed up in LR, but LR doesn't appear to be coded to take advantage of it all, such as cores and threads. Processor speed and up to four cores will help some editing functioins, though some not at all. My rebuilt system is pretty snappy at everything, however some LR editing functions haven't sped up in the slightest. My 51 MPx RAW files are handled zippity-zip, but most editing functions are no quicker than any other file, that is ...Loading... in circles.

Tweaking your BIOS, such as enabling memory XMP, making sure your M.2 drive is running at gen3, etc. makes a difference generally and enhances your overall use of your machine, however it's going to be Adobe getting down to writing fast code that takes advantage of all aspects of our hardware that is going to heal our wounds.

My recent build:

- Intel i7 6700K CPU @ 4Ghz
- Noctua NH-U12S HSF
- 64GB Corsair Vengeance 3000 RAM
- Samsung 950 M.2 NVME 512GB boot drive
- Gigabyte Z170X 7 EU MB
- Nvidia Quatro K2200 GPU
- Samsung 850 Pro SSD 512GB
- Samsung 850 Pro SSD 2TB
- Samsung 850 Pro SSD 1TB
- Antec 850W PSU
- SilverStone TJ07 case
- 8TB Synology NAS

110yd wrote in post #18038717
I believe the Asus Z170A has a M.2 port. Use that instead of the SSD that you are using and
you will see a speed bump.

Regards,

110yd

Some M.2 sockets are not the fast ones, not sure what it is technically that makes the difference ( sorry not technical enough maybe it goes via a SATA Bus rather than PCIe ??) but it really matters , so do your research well before buying.
If yours is the slow type you can buy an ASUS PCIe card to M.2 Adapter I hear thats the only one that delivers full speed. i have one , well built and works with Windows 10 perfectly.

The M.2 you want is the Samsung 950 Pro M.2 NVMe. 512 GB.

I do all my edits for the 2 latests shoots on the Intel 750 PCIe NVMe, and then back them off to a pair of Samsung 850 500GB, no fancy raid , just copies until I achivr them to 2 HGST 4TBs.
There is a cery significant difference editing with Photoshop elements 13, on the Intel 750 ( rough equivalent of the proposed 950 Pro M.2 ) as opposed to editing on the 850s.
Nb buy a fan to cool the M.2 socket or it will hit 100C in 6 seconds! Right by the connection to the MB!

I also run my OS , PSE13, Portraiture, and the NIK pluggins, DPP4, and Office 365 off the 400 GB Intel, plus the latest 2 shoots circa 120GB max. 400GB is the min size for this leaving some free space on the OS drive.