Lightroom/Photoshop: A favour if I possible... (Performance questions)

  • 1
  • Question
  • Updated 2 years ago
  • (Edited)
It's time to upgrade my computer and there's one process that takes me more time than any other - sending two images from LR to PS as layers. With my old i5 Mac Mini, it takes between 35 seconds to a minute to reach a point where I can work on the TIFF. I've timed it with 24MP NEF files, 24MP JPEGs and 18MP CR2s. All the same (weird IMHO). Don't know where the bottle neck is...

If anyone would be so kind as to mimic the process on their system and time it so that I might have a reference I would be very grateful. Don't care if it's a Mac or Windows machine - I'm open to where I go.

With PS editing set to TIF in preferences, just select two shots, right click, edit, edit as layers in Photoshop and see how long it takes. 

Thanks in advance.
Photo of Shane Betts

Shane Betts

  • 155 Posts
  • 53 Reply Likes

Posted 2 years ago

  • 1
Photo of Tom Mickow

Tom Mickow

  • 257 Posts
  • 79 Reply Likes
For what it's worth...

Couple year old Dell E7440 laptop - Win 10 - i7-4600U - 16GB RAM - SSD Drive
Lr CC 2015.6.1
PS CC 2015.5.0
Both apps already open
2 - 20MP CR2 files

15.6 seconds from clicking Open as Layers in Photoshop to the spinning wheel stopping in PS
Photo of Shane Betts

Shane Betts

  • 155 Posts
  • 53 Reply Likes
Wow. OK, that's encouraging. 

Thanks so much for the effort Tom. Like I say, I have no idea where the bottleneck is but I think it's time to trade up to rid myself of it. I wonder what I'll get from the Mac side of things?
Photo of Tom Mickow

Tom Mickow

  • 257 Posts
  • 79 Reply Likes
Yeah, I'm afraid it's a pretty unscientific test with lots of variables.  Just as another data point...

6+ year old desktop - Win 10 - i7 860 - 16GB RAM - OS on SSD - Images on 7,200 RPM SATA drive
Same versions of Lr & PS as before.
Same 2 images as before.

29.8 seconds to be ready to go in PS.
Photo of Shane Betts

Shane Betts

  • 155 Posts
  • 53 Reply Likes
Yeah, I'm afraid it's a pretty unscientific test with lots of variables.
You're right, of course, but given the similarity in times between 24MP NEF and 18MP CR2 on my machine at around 35-40 seconds (the files that take a minute are actually 6MP DNGs), combined with tests opening massive TIF files (3-4 seconds) lead me to believe the bottleneck is either CPU or GPU. Given that LR ignores the GPU on my machine, I think that's where the major issue is. Both your machines are running i7 CPUs and mine an i5 tells me a little. Read/Write speeds on my RAID would fall between your two machines so, combined with the faster opening speeds from big TIFs, tells me it's not largely a read/write issue.

Either way, I run this process maybe 100 times a day. Those 10 or 15 seconds add up while I sit and wait because LR doesn't allow me to queue the images and set them off overnight. I really appreciate your help, so thanks again.
(Edited)
Photo of Jeffrey Tranberry

Jeffrey Tranberry, Sr. Product Manager, Digital Imaging

  • 13968 Posts
  • 1664 Reply Likes
I would suspect you're mostly disk bound (most of the time saving a file and reading the file from disk). SSD or RAID would likely greatly improve the speed.

How to tune Photoshop CS6 for peak performance: http://blogs.adobe.com/crawlspace/2012/10/how-to-tune-photoshop-cs6-for-peak-performance.html
How to tune Lightroom for peak performance: http://helpx.adobe.com/lightroom/kb/optimize-performance-lightroom.html
Performance Troubleshooting: http://helpx.adobe.com/lightroom/kb/performance-hints.html
Photo of Shane Betts

Shane Betts

  • 155 Posts
  • 53 Reply Likes
Thanks Jeffrey but I'm not sure that's it.

My Mac Mini is fitted with an SSD and both my media drive and the drive I use as cache are Thunderbolt RAIDs. Not super fast but not bad either. Given that, as I've said, I can open a TIF file that is three times the size on disk in a fraction of the time, that points not to read/write speed but time taken to debayer the RAW files, in my opinion. Also, given that LR does not use my GPU for this process, I'm leaning towards GPU speed as the killer here. Let's see.

Thanks for the links, BTW. I'll have a thorough read.
(Edited)
Photo of Jeffrey Tranberry

Jeffrey Tranberry, Sr. Product Manager, Digital Imaging

  • 13914 Posts
  • 1649 Reply Likes
Hmm. OK. The GPU is only used to speed up interactivity in the Develop module, so if its doing an export/save process, you're not hitting the GPU, so I have my suspicion that might not be the culprit either.
Photo of Shane Betts

Shane Betts

  • 155 Posts
  • 53 Reply Likes
OK, that's interesting. Is the debayer process done in the CPU? That process is done in PS, it seems.
(Edited)
Photo of Tom Mickow

Tom Mickow

  • 257 Posts
  • 79 Reply Likes
Again, for what it's worth...

Both computers had GPU acceleration turned off in Lr & turned on in PS when I ran the tests posted previously.

Re-running the tests on the laptop with all the combinations of GPU acceleration off & on in both apps resulted in no meaningful differences in the time it took.

Watching resource monitor at the same time showed a sustained spike in CPU usage that lasted the entire time the layers were being created in PS.  Disk IO was bursty at the beginning of the process, presumably when the CR2 files were being read, and then dropped off to basically nothing.

GPU doesn't appear to have had any effect.  CPU & disk look like the main resources in use.
Photo of Shane Betts

Shane Betts

  • 155 Posts
  • 53 Reply Likes
Tom, thank you for going above and beyond. I think you're right. So my major bottleneck would appear to be the Mac Mini's CPU. Well, that begins to make my way forward clearer. 
Photo of John R. Ellis

John R. Ellis, Champion

  • 3372 Posts
  • 844 Reply Likes
Just another data point: On my configuration, it takes about 8 seconds to open two 23 MB .cr2 raws with Open As Layers In Photoshop, with both LR and PS already running.

MacBook Pro
2.8 GHz Intel Core i7 (4 cores)
16 GB 1600 MHz DDR3 memory
All files on internal SSD
Photo of Rory Hill

Rory Hill

  • 236 Posts
  • 33 Reply Likes
On a Win10 PC, i7-6700L, 4GHz, 32GB RAM, SSDs

To open files as layers in Photoshop 2015.5.0 from Lr 2015.6.1 with both apps open:
  • 12 seconds (7DMKII 20MP CR2 files)
  • 16 seconds (D7200 24MP NEF files)
  • 10 seconds (D810 36MP TIFF files)
  • 24 seconds (D810 36MP NEF files)
Photo of lhiapgpeonk

lhiapgpeonk

  • 46 Posts
  • 4 Reply Likes
On a Win10 PC, AMD FX-8350 CPU 8x4GHz, 24 GB RAM (only 667 MHz it appears), System/Cache on SSD, Images on 7200 rpm Disc

2 D7100 NEFs (24MP): ca. 19 seconds (both apps open)
(Edited)
Photo of Shane Betts

Shane Betts

  • 155 Posts
  • 53 Reply Likes
Thanks Tom, Jeffery, John, Rory and lhipgpeonk. Very illuminating.

Seems like CPU has the greatest influence on this particular process, when I previously believed it was GPU.

At 100+ composite images per day of grading, if I can reduce the process time from my current 36 sec on a Mac Mini to something along the lines of 8 sec on a Macbook Pro, that's a saving of 28 seconds per comp, 100 comps a day, three days a week grading adds up to about two and a half hours per week. At $180 per hour (my fantasy hourly rate - someone tell my clients), that's about $1,800 per month. Kinda compelling...
Photo of Rory Hill

Rory Hill

  • 236 Posts
  • 33 Reply Likes
You could try exporting all the images you plan to composite to temporary 16 bit TIFFs at the start of the day while you do something else.  This might speed up the opening in Ps.  You might want to test this.  Of course, this will only work if you know what you want to composite in advance...
Photo of Shane Betts

Shane Betts

  • 155 Posts
  • 53 Reply Likes
Hey Rory. I'll test this today. I guess the time spent building the layers in PS would be offset somewhat by the ability to queue. 

Our world is all about the workaround.
Photo of Rory Hill

Rory Hill

  • 236 Posts
  • 33 Reply Likes
Just to confirm you understand what I am proposing - you use Lr to built the TIFFs in a single batch export which you import back into the Lr library.  You then select the TIFFs you want to composite in Lr and use the same process to open them in Ps.  Because Lr has already converted the raw files to RGB, the TIFFs are loaded into Ps more quickly - the step you identified as a bottleneck.  Overall this workflow is more complicated and takes longer, but if you can batch the creation of the TIFFs at the frontend then you might be ahead.

I know what you mean about workarounds!!
(Edited)
Photo of Shane Betts

Shane Betts

  • 155 Posts
  • 53 Reply Likes
Thanks Rory. Yup. Got it. Sometimes I type faster than I think. And I'm not a fast typist ;-)