Skip to main content
MadManChan2000
Adobe Employee
Adobe Employee
April 26, 2015
Question

GPU notes for Lightroom CC (2015)

  • April 26, 2015
  • 84 replies
  • 195461 views

Hi everyone,

I wanted to share some additional information regarding GPU support in Lr CC.

Lr can now use graphics processors (GPUs) to accelerate interactive image editing in Develop. A big reason that we started here is the recent development and increased availability of high-res displays, such as 4K and 5K monitors. To give you some numbers: a standard HD screen is 2 megapixels (MP), a MacBook Retina Pro 15" is 5 MP, a 4K display is 8 MP, and a 5K display is a whopping 15 MP. This means on a 4K display we need to render and display 4 times as many pixels as on a standard HD display. Using the GPU can provide a significant speedup (10x or more) on high-res displays. The bigger the screen, the bigger the win.

For example, on my test system with a 4K display, adjusting the White Balance and Exposure sliders in Lightroom 5.7 (without GPU support) is about 5 frames/second -- manageable, but choppy and hard to control. The same sliders in Lightroom 6.0 now run smoothly at 60 FPS.

So why doesn't everything feel faster?

Well, GPUs can be enormously helpful in speeding up many tasks. But they're complex and involve some tradeoffs, which I'd like to take a moment to explain.

First, rewriting software to take full advantage of GPUs is a lot of work and takes time. Especially for software like Lightroom, which offers a rich feature set developed over many years and release versions. So the first tradeoff is that, for this particular version of Lightroom, we weren't able to take advantage of the GPU to speed up everything. Given our limited time, we needed to pick and choose specific areas of Lightroom to optimize. The area that I started with was interactive image editing in Develop, and even then, I didn't manage to speed up everything yet (more on this later).

Second, GPUs are marvelous at high-speed computation, but there's some overhead. For example, it takes time to get data from the main processor (CPU) over to the GPU. In the case of high-res images and big screens, that can take a LOT of time. This means that some operations may actually take longer when using the GPU, such as the time to load the full-resolution image, and the time to switch from one image to another.

Third, GPUs aren't best for everything. For example, decompressing sequential bits of data from a file -- like most raw files, for instance -- sees little to no benefit from a GPU implementation.

Fourth, Lightroom has a sophisticated raw processing pipeline (such as tone mapping HDR images with Highlights and Shadows), and running this efficiently on a GPU requires a fairly powerful GPU. Cards that may work with in the Photoshop app itself may not necessarily work with Lightroom. While cards that are 4 to 5 years old may technically work, they may provide little to no benefit over the regular CPU when processing images in Lr, and in some cases may be slower. Higher-end GPUs from the last 2 to 3 years should work better.

So let's clear up what's currently GPU accelerated in Lr CC and what's not:

First of all, Develop is the only module that currently has GPU acceleration whatsoever. This means that other functions and modules, such as Library, Export, and Quick Develop, do not use the GPU (performance should be the same for those functions regardless of whether you have GPU enabled or disabled in the prefs).

Within Develop, most image editing controls have full GPU acceleration, including the basic and tone panel, panning and zooming, crop and straighten, lens corrections, gradients, and radial filter. Some controls, such as local brush adjustments and spot clone/heal, do not -- at least, not yet.

While the above description may be disappointing to some of you, let's be clear: This is the beginning of the GPU story for Lightroom, not the end. The vision here is to expand our use of the GPU and other technologies over time to improve performance. I know that many photographers have been asking us for improved performance for a long time, and we're trying to respond to that. Please understand this is a big step in that direction, but it's just the first step. The rest of it will take some time.

Summary:

1. GPU support is currently available in Develop only.

2. Most (but not all) Develop controls benefit from GPU acceleration.

3. Using the GPU involves some overhead (there's no free lunch). This may make some operations take longer, such as image-to-image switching or zooming to 1:1. Newer GPUs and computer systems minimize this overhead.

4. The GPU performance improvement in Develop is more noticeable on higher-resolution displays such as 4K. The bigger the display, the bigger the win.

5. Prefer newer GPUs (faster models within the last 3 years). Lightroom may technically work on older GPUs (4 to 5 years old) but likely will not benefit much. At least 1 GB of GPU memory. 2 GB is better.

6. We're currently investigating using GPUs and other technologies to improve performance in Develop and other areas of the app going forward.

The above notes also apply to Camera Raw 9.0 for Photoshop/Bridge CC.

Eric Chan

Camera Raw Engineer

This topic has been closed for replies.

84 replies

jwArtWorks
Known Participant
May 14, 2015

I originally installed CC on my HP Laptop while on a trip shooting many photos (Catalog for trip has 8500 RAW images). I needed to turn off the Graphics Processor Option or the develop performance was too slow to use. Switching from image to image took 5 times as long as w/o GCPU, Using the crop tool took 4 times as long as w/o GCPU just to show the bounding grid, etc. I decided to turn off GCPU so it would work faster and it did in fact work better. The other develop tools (brush, spot correction, etc.) seem to be about the same speed as LR5.7.

When I returned home, I installed LR CC on my HP Workstation. I copied the RAW photos to my DROBO (USB 3) and the Catalog to a second DROBO (USB 3). I had no BSOD's or other crashes but it seems like LR CC does not like my video board. The preferences tab tells me there is an error.

This is strange because I also am running Photoshop CC and it seems to be okay with my graphics option.

Before buying my Laptop, I checked the Adobe website and selected a compatible video at extra cost to make sure I would be okay.

When I upgraded to Photoshop CS6 (before I joined the cloud) I upgraded my video card in my HP Workstation so it would be okay with the improved graphics.

Now, I am not sure what to do as there has been no response at all from Adobe. I currently teach classes in both Photoshop and Lightroom software and I have advised everyone on my student mailing list (over 300 students) to stay with LR 5.7 and not upgrade for fear of them having issues after they upgrade. Where do we go from here?

I am a big fan of Adobe (Using Photoshop since version 3 - not CS3 just plain 3 & Lightroom since version 1) and I am okay if this is a bug, I am okay if this is something else, I am just NOT OKAY wondering what is going on and what is being done to help all of us loyal Adobe customers. All of us (or most of us) are willing to accept a problem if it exists and wait for the solution but it is extremely difficult to sit here wondering what is wrong and what to do.

If we all need to go out and buy new video cards, that is not a great thing but then you should have told us this before we upgraded.

Adobe, please communicate with us so we can remain your loyal supporters!

//----------- Laptop Specs ---------------------------

• Windows 8.1 64

• 4th generation Intel(R) Core(TM) i7-4510U Dual Core Processor + 4GB NVIDIA GeForce GTX 850M Graphics

• 17.3-inch diagonal Full HD WLED-backlit Display (1920x1080) Touchscreen

• 16GB DDR3L System Memory (2 Dimm)

• 1TB 5400 rpm Hybrid Hard Drive

• No Additional Office Software

• Security Software Trial

• 4-cell 48WHr Lithium-ion Battery

• Blu-ray writer and SuperMulti DVD burner

• Backlit Keyboard with Fingerprint Reader

• HP TrueVision HD Webcam with Dual Digital Microphone

• Intel 802.11ac WLAN and Bluetooth(R) [1x1]











// ------------- Desktop Specs from LR CC ------------------------

Lightroom version: CC 2015.0.1 [ 1018573 ]

License: Creative Cloud

Operating system: Windows 7 Home Premium Edition

Version: 6.1 [7601]

Application architecture: x64

System architecture: x64

Logical processor count: 4

Processor speed: 3.3 GHz

Built-in memory: 16342.0 MB

Real memory available to Lightroom: 16342.0 MB

Real memory used by Lightroom: 1137.3 MB (6.9%)

Virtual memory used by Lightroom: 1109.8 MB

Memory cache size: 126.3 MB

Maximum thread count used by Camera Raw: 4

Camera Raw SIMD optimization: SSE2,AVX

System DPI setting: 96 DPI

Desktop composition enabled: Yes

Displays: 1) 1920x1080

Input types: Multitouch: No, Integrated touch: No, Integrated pen: No, External touch: No, External pen: No, Keyboard: No

Graphics Processor Info:

Check OpenGL support: Failed

Vendor: ATI Technologies Inc.

Version: 3.3.12002 Core Profile Context 9.12.0.0

Renderer: AMD Radeon HD 5500 Series

LanguageVersion: 4.20

GL_MAX_COMBINED_TEXTURE_IMAGE_UNITS (actual = 32, minimum = 48)

Application folder: C:\Program Files\Adobe\Adobe Lightroom

Library Path: P:\Lightroom\20150415 - Australia & South Pacific Cruise\20150415 - Australia & South Pacific Cruise-2.lrcat

Settings Folder: C:\Users\Joel Weisbrod\AppData\Roaming\Adobe\Lightroom

Installed Plugins:

1) Behance

2) Canon Tether Plugin

3) ColorChecker Passport

4) Facebook

5) Flickr

6) Leica Tether Plugin

7) Nikon Tether Plugin

8) Perfect B&&W 9

9) Perfect Effects 9

10) Perfect Enhance 9

11) Perfect Photo Suite 9

12) Perfect Portrait 9

13) Perfect Resize 9

Config.lua flags: None

Updated Toolkit: Adobe Camera Raw 9.0 for Lightroom 6.0 (build 1014445)

Updated Toolkit: Book Module 6.0 (build 1014445)

Updated Toolkit: Develop Module 6.0 (build 1014445)

Updated Toolkit: Import Module 6.0 (build 1014445)

Updated Toolkit: Library Module 6.0 (build 1014445)

Updated Toolkit: Map Module 6.0 (build 1014445)

Updated Toolkit: Monitor Module 6.0 (build 1014445)

Updated Toolkit: Print Module 6.0 (build 1014445)

Updated Toolkit: Slideshow Module 6.0 (build 1014445)

Updated Toolkit: Web Module 6.0 (build 1014445)

Updated Toolkit: com.adobe.ag.AgNetClient 6.0 (build 1014445)

Updated Toolkit: com.adobe.ag.AgWFBridge 6.0 (build 1014445)

Updated Toolkit: com.adobe.ag.Headlights 6.0 (build 1014445)

Updated Toolkit: com.adobe.ag.LibraryToolkit 6.0 (build 1014445)

Updated Toolkit: com.adobe.ag.MultiMonitorToolkit 6.0 (build 1014445)

Updated Toolkit: com.adobe.ag.archiving_toolkit 6.0 (build 1014445)

Updated Toolkit: com.adobe.ag.bridgetalk 6.0 (build 1014445)

Updated Toolkit: com.adobe.ag.catalogconverters 6.0 (build 1014445)

Updated Toolkit: com.adobe.ag.cef_toolkit 6.0 (build 1014445)

Updated Toolkit: com.adobe.ag.coretech_toolkit 6.0 (build 1014445)

Updated Toolkit: com.adobe.ag.curculio 6.0 (build 1014445)

Updated Toolkit: com.adobe.ag.discburning 6.0 (build 1014445)

Updated Toolkit: com.adobe.ag.email 6.0 (build 1014445)

Updated Toolkit: com.adobe.ag.export 6.0 (build 1014445)

Updated Toolkit: com.adobe.ag.ftpclient 6.0 (build 1014445)

Updated Toolkit: com.adobe.ag.help 6.0 (build 1014445)

Updated Toolkit: com.adobe.ag.iac 6.0 (build 1014445)

Updated Toolkit: com.adobe.ag.imageanalysis 6.0 (build 1014445)

Updated Toolkit: com.adobe.ag.layout_module_shared 6.0 (build 1014445)

Updated Toolkit: com.adobe.ag.pdf_toolkit 6.0 (build 1014445)

Updated Toolkit: com.adobe.ag.sdk 6.0 (build 1014445)

Updated Toolkit: com.adobe.ag.sec 6.0 (build 1014445)

Updated Toolkit: com.adobe.ag.socket 6.0 (build 1014445)

Updated Toolkit: com.adobe.ag.store_provider 6.0 (build 1014445)

Updated Toolkit: com.adobe.ag.substrate 6.0 (build 1014445)

Updated Toolkit: com.adobe.ag.ui 6.0 (build 1014445)

Updated Toolkit: com.adobe.ag.video_toolkit 6.0 (build 1014445)

Updated Toolkit: com.adobe.ag.xml 6.0 (build 1014445)

Updated Toolkit: com.adobe.wichitafoundation 6.0 (build 1014445)

Adapter #1: Vendor : 1002

  D

Participating Frequently
May 12, 2015

Lightroom 6 use model: Wedding photographer and editing service provider.

This post is more on the positive side.  LR6 is up and running smoothly.   An occasional flash between previous image when changing images or zooming.

Still need to test large exporting: 3000+ images.  (Indian weddings)

I have a PC running Win8.1 for OS.

basic i7 3770 CPU

16 gig RAM - matched set 2x 8gig

248 SSD with OS installed and use as working space for Lightroom 6.

Had HD7770 AMD video card that would pass openGL and system check.  I can say it worked.

Upgraded to AMD Fire Pro W5100.

Monitor: 1) Dell U2713H (2560x1440) operating in 10-bit mode, 2) Dell U2412M (1920x1080)

Catalog has standard preview size set to Auto.

Preference has GPU enabled.

Preference: Cache size set to 50 gig


I create catalog based on client since I edit for other wedding photographers.

Therefore my catalogs are many throughout the year.

When I switched graphics card, I noticed an improvement in performance.  The brush is very fluid and snappy - even with gradient/brush and brush used on same image.

LR6 is still a tad glitchy but no lock-ups encountered yet.  Nothing crazy or un-usable.

I have a slight delay 1-2 sec between images -sometimes- when in develop module.

I run the stand-alone version of LR6.

FYI: a gentleman on the Fred Miranda forum has a utilization software package and confirmed when in develop module, GPU use is on or hot.  Everything is being passed through GPU.  sliders/brushes .... I have to go back and verify zoom.

Not all is glooming.  Not a fan boy just a shooter (photographer) getting work done ... and good work at that. 

Participating Frequently
May 11, 2015

This is getting to be a long thread.  It would seem to me someone from Adobe should address the concerns expressed.  I, for one, would like to know that the problems are acknowledged and there is a priority at Adobe to make rapid improvements.

Mike

Participating Frequently
May 11, 2015

I think Adobe can recover from this embarrassing incident if they utilise the fact that they are a large corporation and throw ALL available man power at properly implementing GPU support.  Eric Chan has said that that is the goal and if Adobe can get GPU support working in more areas of LR within a reasonable time then all will be well.

It is recognised in business management circles that communicating well with your customers is extremely good practice.  However, it is often difficult within large corporations where the "bunker" mentality is often common.  I hope Adobe will communicate what their plans are for the good of Adobe and customers.

We will see :-) 

Participating Frequently
May 11, 2015

First thanks for this insightful post.   As systems architect (grid/infra/systems) I frequently have to design for vertical vs horizontal problems so I understand the exercise. 

I do have one question that does puzzle me though that you might have some insight into.   I've noticed thta many operations (face recognition, certain cataloging operations (page/scrolling/optimizing/finding), etc) seem to be bound to a single thread?   in my systems .... with a completely SSD system, 5820k (6 core/12 hyper-4ghz), 16GB-DDR4 (2400) system I find that I max out on operations at around 15-20% utilization.    So I'm trying to understand where these bottlenecks (that are not disk queue, corebound or memory constrained) are?  

P.S.  My catalog is 350k.

tcb1969a
Participant
May 11, 2015

It seems to me that Adobe chose to cheat in order to add better performance to Lightroom.  Instead of writing the performance enhancements into the program, they decided hey, you know there is this GPU thing, why don't we just utilize it, therefor we don't have to do any real work in rewriting Lightroom with performance enhancements.

Here is a no brainer for some of you, not all photographers have extra cash just laying around to throw at a new computer everytime a software manufacturer such as Adobe wants to make there software only for top end computers.  GPU really?  Why, Lightroom 5 was pretty fast without GPU.  What was the thinking?  Apparently there wasn't any.  So now for the 1% that have top of the line computers that can speed along with GPU, you alienate the other 99%.....awesome job.  Who was the genius who thought this was a good idea?  Whoever he is, he should probably be fired and never allowed to work in the industry again.  Just saying.....

Oh and I am not really that mad.......(yes that was sarcasm)

Known Participant
May 11, 2015

Do you really think, Lightroom, Capture One and others go the "GPU-route", because they just want to avoid "any real work"? I guess, they would be glad, if they could stick to the CPU-route. GPU just introduces more possibilities for bugs, which are GPU driver related etc. They went the GPU route, because it seems to be the only way, to get a fast onscreen reaction, especially on high-res displays, which will be more common in the future anyway. I have a pretty old (Intel Q6600 and GTX 750Ti) and a very new PC (6core Haswell E and GTX 970). On both machines, the GPU makes the develop module react much faster, actually realtime, even if I spread Lightroom across my 3 monitors (2x19" and a 1920x1200). Much faster than without GPU and much faster than LR 5.x).I even tried large HDR panos and raw files from a 5DS.

I admit, that under certain circumstances, the brush may be slow. I admit that after zooming it may take a second to get the picture sharp. But I`m pretty sure, this will get better in the future, because, as Eric said, this is only the beginning. And even at that stage, I prefer the GPU enabled LR6 much to LR5 in terms of speed. And my old PC is for sure not one of the "1% that have top line computers".

It would also be helpful, and I do not mean any person in special here, to be as precise as possible in describing what actually is slow. If someone writes "Zooming is slow", what does it mean? Is it stuttering with slow framerates or is it taking time to become sharp? If going from one image to another is slow, what previews do you have, where are they etc.. What GPU/driver you you have? Have you tried other drivers, especially in case of having an AMD card? If brushing is slow, what are your brush settings? Do you brush "exposure", "sharpness" or whatever? Being as precise as possibe will help Adobe find out, what can be improved.

tcb1969a
Participant
May 11, 2015

Yes I really do think that Adobe took the easy way out.  Here are the facts of the case.  On my Machine a MacbookPro Late 2011 Lightroom CC is slower than Lightroom 5, with GPU enabled.  This is starting to be recognized elsewhere as more and more people are realizing they are seeing no real improvement in performance with GPU enabled and more times than not less performance than Lightroom 5.

So those people that were complaining about slow performance with previous Lightroom versions more than likely did not have a fast enough machine in the first place so GPU wouldn't help them achieve it since logically speaking they more than likely don't have a GPU enabled computer or the GPU is too old to be effective.

And just because other companies went to the GPU route doesn't mean really anything.  All it means is that when software encoding gets complicated for introducing speed in a product, the easiest way to go is to have said software utilize the top end hardware such as GPU.  The only problem is, is that when you go that route, always producing software that uses the latest technology or the top end hardware, then the consumer is left either not upgrading the software to the best version of itself or upgrading their computer every 6 months or so since most computers bought off of the shelf are already obsolete.

But with all that said, Lightroom CC has plenty of other bugs and oversights than just the GPU issue.....

sergiolubezky
Participant
May 9, 2015

Hi!
I understand that this issue is affecting different users in different ways. I have the most recent MacBook Pro, with 16GB of memory. Importing with or without the "acceleration" was impossible. So slow that it was ridiculous. I have reinstalled Lightroom 5 and I can say that going back to it was fantastic. I love the speed!  Your Lightroom CC should not even be a release candidate as it is now.

Todd Shaner
Legend
May 9, 2015

slubezky wrote:

I have the most recent MacBook Pro, with 16GB of memory. Importing with or without the "acceleration" was impossible. So slow that it was ridiculous. I have reinstalled Lightroom 5 and I can say that going back to it was fantastic. I love the speed! 

Check your Catalog Preferences. LR 6/CC now uses an 'Auto' Standard Preview Size setting by default, which may be different than the setting you are using in LR5. With my 2560 x 1440 monitor there was an improvement since LR 5 only offers settings of 2,880 or 2,048. My Standard preview size went from 2,880 to the monitor's native 2,560.

May 9, 2015

On my 2015 mb pro retina 2.7 8gb 256ssd after photos have been imported the develop module is very slow and lags.  I've closed and quit all other apps, opened and closed lightroom, turned off sync with LR mobile, face detection and address lookup thinking this would help.  No change.  Just flipping through photos in Develop module to crop takes seconds for each to load.

This is interesting,

Says real memory available to lightroom 8,192mb

Real memory used by LR 1.919mb now up to 2.6gb

Virtual memory used by LR 11,148mb or 11.93 gb and growing, now up to 13.33gb

% cpu 252.80 %

Doesn't seem correct

Participating Frequently
May 9, 2015

For all of you having speed issues, i'll suggest again that for some reason, going to catalog settings and changing the preview size to the smallest (1024px, and i selected medium) has a dramatic improvement in overall image switching, develop stuff, zooming in, 1to1 preview, etc. Maybe it's a caching issue, or the preview setting moves more data from the CPU to GPU??? IDK, but LR is usable for me again. It's still slower, just not stuck in glue. I should add that develop sliders are indeed real time. And brush strokes are slower than LR 5.7.1

Mid 2012 MBP, 2.7Ghz i7, 16GB RAM, 1TB SSD (catalog and previews), 1TB internal HDD for images, nVidia 650M 1024MB, running Yosemite.

The catalog is about 9GB, containing about 600K images. (used to be 12GB, but i deleted all of the history for every photo, which saved quite a bit of space)

deejjjaaaa
Inspiring
May 9, 2015

> For all of you having speed issues, i'll suggest again that for some reason, going to catalog settings and changing the preview size to the smallest (1024px, and i selected medium) has a dramatic improvement in overall image switching, develop stuff, zooming in, 1to1 preview, etc.what

dude - I am using ACR... same code, no stupid catalogs

rjmccor
Participant
May 9, 2015

I have a six month old Mac Pro with a AMD FirePro D500 3072 MB GPU and almost all of the develop functions are significantly slower when I check use the GPU for acceleration.  HUGE disappointment with Lightroom CC!

Known Participant
May 9, 2015

A question to the people that have speed problems with GPU enabled: Did you try GPU acceleration also with ACR9? What about speed there?

rjmccor
Participant
May 9, 2015

Since I¹m using Lightroom as my main processing platform, I don¹t use ACR

natively. Besides, my understanding is that the implementation in Lightroom

is ACR integrated into Lightroom.

Participating Frequently
May 9, 2015

it would be much faster if LR would prerender the next some images BEFORE opening them! or BEFORE zooming in!

niglom
Participant
May 9, 2015

I've just tested LR6 with the new HDR and Panorama processes on my iMac (details below)

8 shot panorama merge start to finish with Graphics Processor turned on 1 min 5 secs, turned off 55 secs - so faster without the GP

5 shot HDR merge 1:02 with GP turned on and off - GP makes no difference

Model Name: iMac

  Processor Name: Intel Core i7

  Processor Speed: 3.4 GHz

  Memory: 16 GB

Chipset Model: AMD Radeon HD 6970M

  VRAM (Total): 2048 MB

Sean H [Seattle branch]
Known Participant
May 9, 2015

Read OP. Gou only affects basic sliders. 

---

[ ◉"]