Skip to main content
Adobe Photoshop Family
Jerry_Syder's profile

613 Messages

 • 

12.4K Points

Mon, Jun 13, 2016 11:39 AM

Lightroom 2015.6 Extremely Slow

I am not sure if this is the best place to post this but I am extremely frustrated! This version is extremely slower than the previous version, which in turn was slower than the one before it. Moving from one image to the next, takes at least 5seconds and adjusting any slider causes Lightroom to freeze, with the lovely "circle of death" reminding me that it's thinking and I should not perform any actions, for 2 seconds or so. I am a very tolerant person but feel like I've had it now! It feels like I am falling out of love with a craft that I once was excited about because editing, which is a very important part of the process, doesn't work. And instead of improving, Lightroom has quickly gotten worse over time! It has taken me 2 and a half days to edit 450 photos, and there's a few more to do but Lightroom has now CRASHED hence my angst here! I have a couple jobs more to edit and I am in a position where I am not seeking after more work because of a backlog of jobs to edit. This is really costing me and I am very angry because I just want to get on with my work. Yes I have a decent system, yes I have plenty of RAM, yes I have a SSD installed. ADOBE, please please please, I just want to edit and enjoy it.

Responses

87 Messages

 • 

1.6K Points

5 years ago

Solution: Minimize LR, wait 5 to 10 seconds, maximize, done. Then it runs fast (or slow...) as we are used to.
Try it.

5 Messages

 • 

114 Points

5 years ago

Just upgraded from LR standalone 6.5 to 6.6.

So far, I have never had any problems or issues with LR after an upgrade.

But after the LR 6.6 upgrade, it feels slower (I can't document it), and LR hangs if I start more than one export process at a time. And it is almost every time.

Also the screen turns black for a while when I move to another photo or do other actions. It just giving me a feeling that is not very stable.

My PC is totally up to date, Win 10 (64bit), 16 GB RAM, Nvidia GTX 980 with latest drivers.



87 Messages

 • 

1.6K Points

Minimize LR, wait 5 to 10 seconds, maximize it and you're able to work for another couple of pictures or actions. And then redo the procedure...

Or do it the best way: Downgrade to 6.5.1.

613 Messages

 • 

12.4K Points

5 years ago

Hi all. What I've done is uninstall all of my AMD products and reinstalled them(most importantly the graphic driver) and its working fine. As @stefan said, fast(or slow) as it used to. My rant is over :-)

57 Messages

 • 

1.2K Points

5 years ago

Moved  my cat and preview folders to a my fastest ssd (Samsung 950 pro). That did nothing so I moved my raw files (just one folder) to the same ssd.  Some improvement but still extremely laggy: taking 5 seconds to apply a develop preset for instance.  Applying and moving a grad felt like I was back on my i7 920 from 6 years ago.  Switching ON the graphics card improved grad speed, but it slowed down using the brush. WTF?   
Lightroom memory usage crept up whilst using it - 4gb to 12gb. over about 20 mins. 
I can also confirm that "turning it off and on again" helps with speed. 

13 Messages

 • 

288 Points

5 years ago

I've also noticed some graphical "ghosting" (not sure what to call it) where you can see some overlay of parts of the software when performing some step that I've never seen until now. For example, switching from Develop to Library module, I can see a faint, translucent box of something in the screen while it's switching over.  It pegs my CPU and takes about 5 seconds to come back to life and then the little translucent box disappears.  I also see crazy red flashes when adjusting the radial filter oval - I think it's related to the red coloring LR uses to show the mask.  It does it the first few times I adjust the filter and then they go away.  Trying to set white/black points (holding option key while sliding white and black adjustment sliders) is unusable to me now since it takes literally 3-4 seconds each time I move the slider and by the time it starts showing me parts of the image that are either white or black, I've already moved beyond it because of the severe lag. So frustrating.  It really feels like they didn't do any thorough QA/testing on this release.  I'm running what I think is a pretty standard computer setup for photo editors and I feel like I'm running a beta version of LR.  I thought I had actually found a solution which was turning off GPU in prefs, as things started acting normally again - everything was very speedy.  But that soon faded and after a few minutes, things were back to being very laggy with terrible performance so I enabled GPU again.  I'm going to try the suggestion above to reset my preferences file - I just haven't had time yet.  Hopefully that will cure the issues I'm having but I'm doubtful and really shouldn't have to go to those lengths to get a dot release working as it should.

10 Messages

 • 

154 Points

5 years ago

please try smart previews i think it will be helpful for you ...........

13 Messages

 • 

288 Points

5 years ago

Not sure who that was directed to but I've been using smart previews since LR5. It isn't the cause of any of the performance issues I'm encountering.

51 Messages

 • 

1.7K Points

Lr doesn't use smart previews until it doesn't have access to the original files.  If you temporarily change the name of the folder where the original files are stored and then go through culling/develop module it will go significantly faster.  My testing has shown a 4x improvement in moving between photos.

87 Messages

 • 

1.6K Points

5 years ago

Solved it my way:
Uninstalled and reinstalled CC 2015.5.1. It is running again as we are used to.

BTW: Exporting in 2015.6 is a bit speedier. Never thought that. But Usability is what counts in this case.

27 Messages

 • 

470 Points

5 years ago

Yup. Same problem as everyone else. Moving between modules is terribly slow. Trying to drag out or move elliptical adjustments, LR lags hugely. Working exclusively with 20.2MP DNGs, for what it's worth.

Macbook Pro (10,2)
13" Retina
Intel Core i7 (2 cores)
8GB RAM
1536MB VRAM
512GB SSD

150 Messages

 • 

2.9K Points

5 years ago

4K display?

27 Messages

 • 

470 Points

Nope. 13" Retina is 2880 x 1800.

26 Messages

 • 

350 Points

Hello
The whole point of Lightroom is to use low res proxies whilst editing.
To run huge 1:1 proxies with 4 or 5k screens will bring any system to its knees!  Your file sizes are huge, so use lower size proxies.
I run 1920x1200 and I find that I have very few problems with Lightroom speed on 5D3 files, except when cloning, especially when I have multiple overlaying clones, to remove objects and overhead wires. Use of the GPU has very little general effect except for a couple of processes. I bought and tried a pretty powerful GPU and found that it was no better than my very ancient AMD HD5450.
I use a 6 year old home built quad core 16gb ram and a Samsung SSD with Win 10 and Win 7 on the same computer. Standard hard drives for storage.
MDE

13 Messages

 • 

288 Points

And what do you say to those of us who have been working the same exact way, same exact hardware specs, with the same exact types/sizes of images for months/years and only now are experiencing terrible performance and buggy UI behavior with the latest LR update?

27 Messages

 • 

470 Points

+1

Champion

 • 

2.3K Messages

 • 

38.2K Points

The issue being discussed here appears to be due to a memory leak, which is completely independent of monitor resolution. https://forums.adobe.com/message/8812806#8812806

5 Messages

 • 

114 Points

I have just uninstalled LR 6.6, and reinstalled with the LR 6.5.1 patch.
It's like... ahh, much faster, multiple export processes without hanging, a huge upgrade to LR 6.6.

I could work with the new funny import dialogue in LR 6.2, but LR 6.6 is imho the worst LR upgrade ever from adobe.

Previous patches to LR can be downloaded here:
https://helpx.adobe.com/lightroom/kb/lightroom-downloads.html

26 Messages

 • 

350 Points

Hello

I have no answer to the question David Erfurd asked, but I cannot see how some systems have a memory leak and others don't running Win 7 or Win 10

Now it does seem that my comments were a hostage to fortune as directly after I was panning around a 1:1 @1920x1200 image, the system became very notchy and the CPU started to howl. I minimised LR 6.6 and the CPU stopped howling. I maximised about 2 mins on and did the same panning and all was fine and then became notchy. I was doing no editing just jumping from image to image at 1:1 waited for a sec or two for complete redraw and scrolled. The images had been edited previously.

Not really aware of this behaviour before, but I have to say I have not done this before either.

MDE

26 Messages

 • 

350 Points

Hello again
All my tests above were with Win 7 Pro
I re-booted to my Win 10 pro setup and did the same panning with the same files in Lightroom 6.6.
Well the CPU  howls, but panning is not 'notchy' after the file has loaded, 1-2 secs. Lightroom in this regard is much more responsive in Win 10. In both cases GPU is off.

MDE

PS now rebooted back into Win 7 pro and did the same as when I had the 'notchy' problem. Now no problem, Win 7 seems to be as good as Win 10.

Cannot explain any of this


2 Messages

 • 

72 Points

Slow, Slow,Slow, Slow,Slow, Slow,Slow, Slow,Slow, Slow,Slow, Slow,Slow, Slow,Slow, Slow,Slow, Slow,Slow, Slow,Slow, Slow.  So sick of dealing with this every time there is an upgrade.  

613 Messages

 • 

12.4K Points

Hi all. What I've done is uninstall all of my AMD products and reinstalled them(most importantly the graphic driver) and its working fine now

26 Messages

 • 

350 Points

Hello

Now, It seems that there is a validity in the many suggestions to stop work for 2 mins if the system becomes 'notchy'. I have done this several times and after resume, panning a 1:1 image at 1920x1200 is instant and no CPU howl, but seems to get worse in a few mins. Panning about does tax the system as it is continually processing and redrawing, rapidly changing parts of the image. Is there some sort of caching of view memory going on?

MDE

1 Message

 • 

60 Points

Seit dem neuesten Update ist das Lightroom leider sehr sehr langsam.
Bitte macht etwas daran, dass dies mit einem neuen Update wieder schnelle geht.

2 Messages

 • 

70 Points

Have you called Adobe?  The techs there ran me through all kinds of diagnostics and it really helped my speed.  It is worth a try.  Good luck!

1 Message

 • 

60 Points

I noticed a slow down with 2015.6  Some pictures taking a minute or more to load(.ORF) files. Disabled the GPU and things speed up!

15 Messages

 • 

434 Points

after spending hour with adobe on the phone and online, i went back to the previous version on their recommendation with gpu off, i just can't believe these guys roll product like this.

2 Messages

 • 

70 Points

5 years ago

I just got off the phone with Adobe and they helped me by doing this.

Shut down Lightroom
Go to your Library > Preferences
Find the file com.adobe.Lightroom6.plist
Rename that file to com.adobe.Lightroom6.old.plist
Restart Lightroom!

For me it works perfectly and my speed is back up to normal.  I am running a Mac OS 10.10.5

Good luck!

27 Messages

 • 

470 Points

Thanks, Hayley. Can you be more specific? Where is this preferences file? I'm on a Mac/10.11.4, and after scouring user/library/preferences/adobe/ I can't find such a file.

57 Messages

 • 

1.2K Points

Can anyone from adobe offer insight into this. Cant find a plist file on my windows system that relates to lightroom.

Employee

 • 

1.7K Messages

 • 

32.4K Points

You can do this by holding down Shift + Option/Alt while launching Lightroom. In the following dialog, click the "Rest Preferences" button.

Principal Scientist, Adobe Lightroom

57 Messages

 • 

1.2K Points

THanks Simon.
This didn't help, though. (Worked OK for a little while, then slowed down. Showing 17gb RAM in use)

26 Messages

 • 

350 Points

Hello

I did some tests just panning at 1:1 1920x1200 images that have been edited, lens transforms applied as well as some with quite a lot of cloning. This taxes the whole system as it has to continually apply the edits to a changing view. Initially all is well CPU never goes beyond 50%, with no screaming fans and ram is 3.64 (2.60 when Lightroom is not on). Redraw is pretty instant click to go to normal view instant. This continues for about 5 images with CPU and ram increasing, the system gets notchy, but still usable. At the 6th image panning just gets bogged down. Clicking to return to normal view is ignored. Ram about 8GB, CPU spiking but averaging below 50%, with fans running. Minimisng  and maximising brings the response back but not for long. Restarting is best.  This is without GPU.

Turning on GPU. The panning never gets bogged down, but the redraw is very slow and is done tile by tile from the start, rather than the view. MY GPU is a AMD HD5450 and is old. . The CPU seems to work even harder (continual fans form the start) and ram use goes up to 9GB and over. From my point of view using the GPU slows things down overall and seems to use more resources. I use Win 7, 16gb of ram and a quad core. All this is 6 years old. On the whole this system is fine. It is not used professionally.

MDE

Employee

 • 

1.7K Messages

 • 

32.4K Points

> "quite a lot of cloning"
This is known to be very taxing to Lightroom, especially if you have a lot of them.

Principal Scientist, Adobe Lightroom

Employee

 • 

1.7K Messages

 • 

32.4K Points

@Gethin
Can you post your Lightroom>Help>System Info... here please. What is the total amount of RAM on the machine? Are you able to consistently reproduce the issue?

Principal Scientist, Adobe Lightroom

26 Messages

 • 

350 Points

Hello

Thanks for your reply.

I have a CPU trace and attach it

The machine is home built 16gb Ram with Quad core 2.93GHz AMD HD5450 video I created a test catalogue with 7 edited images, a couple with minimal processing 3 with very heavy cloning to get rid of objects and the rest in between.

I allowed Lightroom to make the 1:1 previews at 1920x1200 best quality. All catalogues and caches are on the SSD. Cache is 100gB  Video cache is 10gB

Closed Lightroom and started task manager. Initial PC state 3.15gB ram 0 CPU.

Opened Lightroom clicked on first image and zoomed 100%, proceeded to pan about to the extremes of the image. A little notchy, but OK redraw within a sec. Next image started 100% zoom and within a sec. Continued panning and did the same for all images. System got progressively more unresponsive and redraw lagged by secs.

You can see a main peak when the image switched. It seemed to make very little difference what the image was as.I had by the end gone back to the first image ( minimal processing) The CPU trace does not show it but the screen did not by now respond to mouse movement without a large delay with redraw taking time and by now a large delay in switching images, or clicking on the screen to go to normal preview.

Images 3 4 and 7 have large amounts of cloning, to get rid of bins, chairs and overhead wires

MDE

SYSTEM INFO

Lightroom version: 6.6 [ 1078672 ]
License: Perpetual
Operating system: Windows 7
Version: 6.1
Application architecture: x64
System architecture: x64
Logical processor count: 4
Processor speed: 2.9 GHz
Built-in memory: 16374.1 MB
Real memory available to Lightroom: 16374.1 MB
Real memory used by Lightroom: 934.8 MB (5.7%)
Virtual memory used by Lightroom: 936.7 MB
Memory cache size: 866.0 MB
Maximum thread count used by Camera Raw: 4
Camera Raw SIMD optimization: SSE2
System DPI setting: 96 DPI
Desktop composition enabled: No
Displays: 1) 1920x1200
Input types: Multitouch: No, Integrated touch: No, Integrated pen: No, External touch: No, External pen: No, Keyboard: No

Graphics Processor Info:
AMD Radeon HD 5450

Check OpenGL support: Passed
Vendor: ATI Technologies Inc.
Version: 3.3.13399 Core Profile Context 15.201.1151.1005
Renderer: AMD Radeon HD 5450
LanguageVersion: 4.40


Application folder: C:\Program Files\Adobe\Adobe Lightroom
Library Path: E:\Test\Test.lrcat
Settings Folder: C:\Users\mengles\AppData\Roaming\Adobe\Lightroom

Installed Plugins:
1) Canon Tether Plugin
2) ColorChecker Passport
3) Facebook
4) Flickr
5) Leica Tether Plugin
6) Nikon Tether Plugin
7) rc Xmp Crop

Config.lua flags: None

Adapter #1: Vendor : 1002
 Device : 68f9
 Subsystem : 3661043
 Revision : 0
 Video Memory : 1010
AudioDeviceIOBlockSize: 1024
AudioDeviceName: Speakers (Realtek High Definition Audio)
AudioDeviceNumberOfChannels: 2
AudioDeviceSampleRate: 44100
Build: LR5x102
Direct2DEnabled: false
GL_ACCUM_ALPHA_BITS: 0
GL_ACCUM_BLUE_BITS: 0
GL_ACCUM_GREEN_BITS: 0
GL_ACCUM_RED_BITS: 0
GL_ALPHA_BITS: 8
GL_BLUE_BITS: 8
GL_DEPTH_BITS: 24
GL_GREEN_BITS: 8
GL_MAX_3D_TEXTURE_SIZE: 2048
GL_MAX_TEXTURE_SIZE: 16384
GL_MAX_TEXTURE_UNITS: 8
GL_MAX_VIEWPORT_DIMS: 16384,16384
GL_RED_BITS: 8
GL_RENDERER: AMD Radeon HD 5450
GL_SHADING_LANGUAGE_VERSION: 4.40
GL_STENCIL_BITS: 8
GL_VENDOR: ATI Technologies Inc.
GL_VERSION: 4.5.13399 Compatibility Profile Context 15.201.1151.1005
GPUDeviceEnabled: false
OGLEnabled: true
GL_EXTENSIONS: GL_AMDX_debug_output GL_AMDX_vertex_shader_tessellator GL_AMD_conservative_depth GL_AMD_debug_output GL_AMD_depth_clamp_separate GL_AMD_draw_buffers_blend GL_AMD_multi_draw_indirect GL_AMD_name_gen_delete GL_AMD_performance_monitor GL_AMD_pinned_memory GL_AMD_query_buffer_object GL_AMD_sample_positions GL_AMD_seamless_cubemap_per_texture GL_AMD_shader_stencil_export GL_AMD_shader_trace GL_AMD_texture_cube_map_array GL_AMD_texture_texture4 GL_AMD_transform_feedback3_lines_triangles GL_AMD_vertex_shader_layer GL_AMD_vertex_shader_tessellator GL_AMD_vertex_shader_viewport_index GL_ARB_ES2_compatibility GL_ARB_ES3_1_compatibility GL_ARB_ES3_compatibility GL_ARB_arrays_of_arrays GL_ARB_base_instance GL_ARB_blend_func_extended GL_ARB_buffer_storage GL_ARB_clear_buffer_object GL_ARB_clear_texture GL_ARB_clip_control GL_ARB_color_buffer_float GL_ARB_compatibility GL_ARB_compressed_texture_pixel_storage GL_ARB_compute_shader GL_ARB_conditional_render_inverted GL_ARB_conservative_depth GL_ARB_copy_buffer GL_ARB_copy_image GL_ARB_cull_distance GL_ARB_debug_output GL_ARB_depth_buffer_float GL_ARB_depth_clamp GL_ARB_depth_texture GL_ARB_derivative_control GL_ARB_direct_state_access GL_ARB_draw_buffers GL_ARB_draw_buffers_blend GL_ARB_draw_elements_base_vertex GL_ARB_draw_indirect GL_ARB_draw_instanced GL_ARB_enhanced_layouts GL_ARB_explicit_attrib_location GL_ARB_explicit_uniform_location GL_ARB_fragment_coord_conventions GL_ARB_fragment_layer_viewport GL_ARB_fragment_program GL_ARB_fragment_program_shadow GL_ARB_fragment_shader GL_ARB_framebuffer_no_attachments GL_ARB_framebuffer_object GL_ARB_framebuffer_sRGB GL_ARB_geometry_shader4 GL_ARB_get_program_binary GL_ARB_get_texture_sub_image GL_ARB_gpu_shader5 GL_ARB_gpu_shader_fp64 GL_ARB_half_float_pixel GL_ARB_half_float_vertex GL_ARB_imaging GL_ARB_instanced_arrays GL_ARB_internalformat_query GL_ARB_internalformat_query2 GL_ARB_invalidate_subdata GL_ARB_map_buffer_alignment GL_ARB_map_buffer_range GL_ARB_multi_bind GL_ARB_multi_draw_indirect GL_ARB_multisample GL_ARB_multitexture GL_ARB_occlusion_query GL_ARB_occlusion_query2 GL_ARB_pipeline_statistics_query GL_ARB_pixel_buffer_object GL_ARB_point_parameters GL_ARB_point_sprite GL_ARB_program_interface_query GL_ARB_provoking_vertex GL_ARB_query_buffer_object GL_ARB_robust_buffer_access_behavior GL_ARB_sample_shading GL_ARB_sampler_objects GL_ARB_seamless_cube_map GL_ARB_seamless_cubemap_per_texture GL_ARB_separate_shader_objects GL_ARB_shader_atomic_counters GL_ARB_shader_bit_encoding GL_ARB_shader_image_load_store GL_ARB_shader_image_size GL_ARB_shader_objects GL_ARB_shader_precision GL_ARB_shader_stencil_export GL_ARB_shader_storage_buffer_object GL_ARB_shader_subroutine GL_ARB_shader_texture_image_samples GL_ARB_shader_texture_lod GL_ARB_shading_language_100 GL_ARB_shading_language_420pack GL_ARB_shading_language_packing GL_ARB_shadow GL_ARB_shadow_ambient GL_ARB_stencil_texturing GL_ARB_sync GL_ARB_tessellation_shader GL_ARB_texture_barrier GL_ARB_texture_border_clamp GL_ARB_texture_buffer_object GL_ARB_texture_buffer_object_rgb32 GL_ARB_texture_buffer_range GL_ARB_texture_compression GL_ARB_texture_compression_bptc GL_ARB_texture_compression_rgtc GL_ARB_texture_cube_map GL_ARB_texture_cube_map_array GL_ARB_texture_env_add GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_ARB_texture_float GL_ARB_texture_gather GL_ARB_texture_mirror_clamp_to_edge GL_ARB_texture_mirrored_repeat GL_ARB_texture_multisample GL_ARB_texture_non_power_of_two GL_ARB_texture_query_levels GL_ARB_texture_query_lod GL_ARB_texture_rectangle GL_ARB_texture_rg GL_ARB_texture_rgb10_a2ui GL_ARB_texture_snorm GL_ARB_texture_stencil8 GL_ARB_texture_storage GL_ARB_texture_storage_multisample GL_ARB_texture_swizzle GL_ARB_texture_view GL_ARB_timer_query GL_ARB_transform_feedback2 GL_ARB_transform_feedback3 GL_ARB_transform_feedback_instanced GL_ARB_transform_feedback_overflow_query GL_ARB_transpose_matrix GL_ARB_uniform_buffer_object GL_ARB_vertex_array_bgra GL_ARB_vertex_array_object GL_ARB_vertex_attrib_64bit GL_ARB_vertex_attrib_binding GL_ARB_vertex_buffer_object GL_ARB_vertex_program GL_ARB_vertex_shader GL_ARB_vertex_type_10f_11f_11f_rev GL_ARB_vertex_type_2_10_10_10_rev GL_ARB_viewport_array GL_ARB_window_pos GL_ATI_draw_buffers GL_ATI_envmap_bumpmap GL_ATI_fragment_shader GL_ATI_separate_stencil GL_ATI_texture_compression_3dc GL_ATI_texture_env_combine3 GL_ATI_texture_float GL_ATI_texture_mirror_once GL_EXT_abgr GL_EXT_bgra GL_EXT_bindable_uniform GL_EXT_blend_color GL_EXT_blend_equation_separate GL_EXT_blend_func_separate GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_compiled_vertex_array GL_EXT_copy_buffer GL_EXT_copy_texture GL_EXT_direct_state_access GL_EXT_draw_buffers2 GL_EXT_draw_instanced GL_EXT_draw_range_elements GL_EXT_fog_coord GL_EXT_framebuffer_blit GL_EXT_framebuffer_multisample GL_EXT_framebuffer_object GL_EXT_framebuffer_sRGB GL_EXT_geometry_shader4 GL_EXT_gpu_program_parameters GL_EXT_gpu_shader4 GL_EXT_histogram GL_EXT_multi_draw_arrays GL_EXT_packed_depth_stencil GL_EXT_packed_float GL_EXT_packed_pixels GL_EXT_pixel_buffer_object GL_EXT_point_parameters GL_EXT_polygon_offset_clamp GL_EXT_provoking_vertex GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_separate_specular_color GL_EXT_shader_image_load_store GL_EXT_shader_integer_mix GL_EXT_shadow_funcs GL_EXT_stencil_wrap GL_EXT_subtexture GL_EXT_texgen_reflection GL_EXT_texture3D GL_EXT_texture_array GL_EXT_texture_buffer_object GL_EXT_texture_compression_bptc GL_EXT_texture_compression_latc GL_EXT_texture_compression_rgtc GL_EXT_texture_compression_s3tc GL_EXT_texture_cube_map GL_EXT_texture_edge_clamp GL_EXT_texture_env_add GL_EXT_texture_env_combine GL_EXT_texture_env_dot3 GL_EXT_texture_filter_anisotropic GL_EXT_texture_integer GL_EXT_texture_lod GL_EXT_texture_lod_bias GL_EXT_texture_mirror_clamp GL_EXT_texture_object GL_EXT_texture_rectangle GL_EXT_texture_sRGB GL_EXT_texture_sRGB_decode GL_EXT_texture_shared_exponent GL_EXT_texture_snorm GL_EXT_texture_storage GL_EXT_texture_swizzle GL_EXT_timer_query GL_EXT_transform_feedback GL_EXT_vertex_array GL_EXT_vertex_array_bgra GL_EXT_vertex_attrib_64bit GL_IBM_texture_mirrored_repeat GL_KHR_context_flush_control GL_KHR_debug GL_KHR_robust_buffer_access_behavior GL_KHR_robustness GL_KTX_buffer_region GL_NV_blend_square GL_NV_conditional_render GL_NV_copy_depth_to_color GL_NV_copy_image GL_NV_depth_buffer_float GL_NV_explicit_multisample GL_NV_float_buffer GL_NV_half_float GL_NV_primitive_restart GL_NV_texgen_reflection GL_NV_texture_barrier GL_OES_EGL_image GL_SGIS_generate_mipmap GL_SGIS_texture_edge_clamp GL_SGIS_texture_lod GL_SUN_multi_draw_arrays GL_WIN_swap_hint WGL_EXT_swap_control

22 Messages

 • 

446 Points

Well, I too need to share my experience with Lightroom CC 2015.6 on brand new and powerful iMac on which I experience similar performance issues. Is it my setup or is it indeed the application that needs refinements?

Until 2 months ago I was using a 
  • MacBook Pro mid 2012, retina
  • 16GB RAM
  • 2,7 GHz Core i7 processor.
  • 750GB SSD
  • NVIDIA GeForce GT 650M 1024 MB
  • OS X El Capitan 10.11.3
  • Adobe Creative Cloud - applications always up to date
  • Using mostly Lightroom and Photoshop (I'm a photographer, that's my job & passion)
Well, this is a pretty decent computer, but over the last couple of months or a year it has been running progressively slower and slower when running Lightroom. Photoshop was behaving more or less OK having in mind the specs and age of the MAC. But eventually Lightroom became so slow, I cant even describe the slowness. I as looking at the spinning wheel more time than working on an image. Lightroom was slow in all modules. Normally I also have Mail and Safari opened and some times Photoshop. Back in time, some 6 months ago, I first started closing one of those apps to slightly improve LR's performance. Then I had to start closing all applications and only leave LR running. My computer became a dedicated machine to Lightroom, only to try and have some work done at the end of the day. 

Strangely enough, there was always free RAM (I use Bjango's iStat Menus to constantly monitor RAM and CPU in the OS's menu bar)...some times as much as 25%-40% free RAM. But Lightroom was behaving as if there was none. 

So a few weeks ago I decided that my old pal the MacBook Pro has to be retired, although he was performing VERY WELL with all other applications...But I understand that Adobe applications are complex image editing power softwares and resource hungry. So I did a huge investment in the latest and greatest, fully loaded iMac...

Two months ago I received my iMac and I've been using it intensively ever since, doing my observations and taking notes. And after 2 weeks I had to reach out to the forums and cry out my frustrations. Because there are such...and as I see, I'm not alone...First the iMac's specs:
  • iMac 5k, late 2015 model, 27", fully tuned and loaded with 
  • 64GB RAM;
  • 4,0 GHz Core i7;
  • 1TB SSD (no fusion drive) by the way it's 4x faster in read & write times than my old MacBook Pro. Performance was measured with Blackmagic Disk Speed Test v. 2.2.2 and the iMac's SSD exceeds the scale with over 1200MB/s write and 1900MB/s read speeds;
  • AMD Radeon R9 M395X 4096 MB;
  • OS X El Capitan 10.11.3
  • Adobe Creative Cloud - applications always up to date (currently LR CC is 2015.4, CR is 9.4, PS is 2015.1.2)
Well, overall performance is better, indeed. But it's far from what I expected and hoped for. Don't get me wrong -- the iMac is performing AMAZINGLY well with all other applications. But with Lightroom I still see the spinning wheel a lot of times. For the folders with images that I'm currently working on I render full resolution 1:1 previews +  Smart Previews (so in fact I'm working on the internal iMac SSD). Rendering edits lags. The spot removal tool is so badly slow and lagging, that I prefer to export the file to Photoshop and clean it there. How is this possible?

Before I get asked let me answer: yes, I do use the graphics processor (the option is selected). I tried both options.

13 Messages

 • 

288 Points

5 years ago

This is getting stupid.  I've tried resetting my prefs following the steps provided in earlier posts and on Adobe's help site, uninstall/reinstall LR, turn off/on GPU, etc. and still experiencing awful lag/performance with this latest update.  Just trying to erase a part of a gradient mask using the brush takes like 5 seconds each stroke before it catches up.  It never behaved like this before this update.  I guess I'll try uninstalling and seeing if I can reinstall the last LR version prior to 2015.6 until they release a .1 patch. 

150 Messages

 • 

2.9K Points

same here

26 Messages

 • 

350 Points

5 years ago

Hello

It took me a good three hours to do  this cloning on Lightroom 6.6, so from my point of view it is usable. It was slow mainly because of the zooming in and out, but that does not surprise, because the job was somewhat ambitious I have many more complaints about how limited the cloning toolset is. There is also a problem with overlaying clones using a mixture of clone and heal. You get colour fringing at the selection edges

 I expect that the system I have is just about OK for what camera and screen I use and as amateur the small amount of work I do, which is about 4000 images a year. Running 4k systems means that file sizes are huge and quite possibly only a render farm type of machine will cope, but I am very aware of how much high powered machines cost and people still finding that they seem inadequate.

Apologies if this irritates some people.

MDE

Employee

 • 

1.7K Messages

 • 

32.4K Points

5 years ago

It seems to be a common theme that spot removal slows things down. The team has an existing bug tracking that. I'll talk to the team to see we can do something about it. There is not likely a quick solution.

Can you confirm this by selecting all the relevant photos, Auto Sync on, and go to the spot removal tool, toggle the Spot Removal panel switch to off. And try again to see if it helps.

Principal Scientist, Adobe Lightroom

171 Messages

 • 

3.9K Points

BTW. the new transform tool also gets very jerky, if you have local adjustments already applied. No problem in ACR btw.

26 Messages

 • 

350 Points

Hello Simon

Thanks for the reply.

As far as I can see from my panning tests, it does not matter too much if the spot tool is used or not. The first image of the oranges has really minimal processing, just lens correction sharpening/noise and camera calibration. This image was fine at the start of the panning sequence, but the computer was pretty well bogged down by the time I returned to it, as the 8th image. Giving the whole business a small rest, brings responsiveness back, but not for long

I did reinstall Lightroom 6.0. This seems marginally more responsive overall. I also have upgraded to 6.5, which I think is not very different from 6.6. I am processing as far as I can see 1920x1200 13mb 16 bit images with an old computer and not having too many problems. I imagine Adobe has systems that cope very well with 4k screens and such. It should perhaps give an idea of what is needed to process large pixel previews

MDE

26 Messages

 • 

350 Points

Hello Simon

Call me a sad old fool, but I did another panning test and curiously this time, every thing went pretty smoothly until the 5th image, when the system began to lock up.

I took a system info before and after the test and after 5 mins rest. Why is Lightroom using so much virtual memory when there is still usable system ram?

These are the numbers at the start

Built-in memory: 16374.1 MB
Real memory available to Lightroom: 16374.1 MB
Real memory used by Lightroom: 962.8 MB (5.8%)
Virtual memory used by Lightroom: 970.9 MB
Memory cache size: 839.8 MB

These are the numbers at the end.

Built-in memory: 16374.1 MB
Real memory available to Lightroom: 16374.1 MB
Real memory used by Lightroom: 4240.0 MB (25.8%)
Virtual memory used by Lightroom: 4835.0 MB
Memory cache size: 2605.7 MB

Lightroom is using more virtual memory than real memory.

After 5 mins rest

Built-in memory: 16374.1 MB
Real memory available to Lightroom: 16374.1 MB
Real memory used by Lightroom: 2739.9 MB (16.7%)
Virtual memory used by Lightroom: 2901.0 MB
Memory cache size: 0.0 MB

There seem to be a lot of real memory not being used!

Lightroom seems to resort to virtual memory pretty early.

My Windows virtual memory is on the SSD as are all caches.

Is windows managing memory use or Lightroom?

I am now back on Lightroom 6.6, as from what I can see, there is not a lot of difference in performance between the iterations.

MDE


57 Messages

 • 

1.2K Points

@simon

Yes it happens all the time.  I get about 15 mins use before I have to restart LR.  This does not appear to happen (or is less obvious) if I'm using smart previews.  Also the performance of LR is better when I use it through remote desktop on a laptop screen of 1920x1080.  Using LR at reduced window size also greatly improves performance.  If you'd like me to screen grab me working on pics, with resource monitor I'm happy to.


Lightroom version: CC 2015.6 [ 1078672 ]License: Creative Cloud
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: 65436.0 MB
Real memory available to Lightroom: 65436.0 MB
Real memory used by Lightroom: 2391.0 MB (3.6%)
Virtual memory used by Lightroom: 2584.0 MB
Memory cache size: 1443.5 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) 1920x1200, 3) 1360x768
Input types: Multitouch: No, Integrated touch: No, Integrated pen: No, External touch: No, External pen: No, Keyboard: No

Graphics Processor Info: 
GeForce GTX 970/PCIe/SSE2

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


Application folder: C:\Program Files\Adobe\Adobe Lightroom
Library Path: N:\LR5 REAL ESTATE\LR5 REAL ESTATE-2.lrcat
Settings Folder: C:\Users\Gethin\AppData\Roaming\Adobe\Lightroom

Installed Plugins: 
1) Canon Tether Plugin
2) Export to Autopano Giga
3) Facebook
4) Flickr
5) jf Timelapse Support
6) Leica Tether Plugin
7) Nikon Tether Plugin

Config.lua flags: None

Adapter #1: Vendor : 10de
Device : 13c2
Subsystem : 366a1458
Revision : a1
Video Memory : 4008
Adapter #2: Vendor : 1414
Device : 8c
Subsystem : 0
Revision : 0
Video Memory : 0
AudioDeviceIOBlockSize: 1024
AudioDeviceName: Speakers (Realtek High Definition Audio)
AudioDeviceNumberOfChannels: 2
AudioDeviceSampleRate: 44100
Build: LR5x102
Direct2DEnabled: false
GL_ACCUM_ALPHA_BITS: 16
GL_ACCUM_BLUE_BITS: 16
GL_ACCUM_GREEN_BITS: 16
GL_ACCUM_RED_BITS: 16
GL_ALPHA_BITS: 0
GL_BLUE_BITS: 8
GL_DEPTH_BITS: 24
GL_GREEN_BITS: 8
GL_MAX_3D_TEXTURE_SIZE: 2048
GL_MAX_TEXTURE_SIZE: 16384
GL_MAX_TEXTURE_UNITS: 4
GL_MAX_VIEWPORT_DIMS: 16384,16384
GL_RED_BITS: 8
GL_RENDERER: GeForce GTX 970/PCIe/SSE2
GL_SHADING_LANGUAGE_VERSION: 4.50 NVIDIA
GL_STENCIL_BITS: 8
GL_VENDOR: NVIDIA Corporation
GL_VERSION: 4.5.0 NVIDIA 358.91
GPUDeviceEnabled: false
OGLEnabled: true
GL_EXTENSIONS: GL_AMD_multi_draw_indirect GL_AMD_seamless_cubemap_per_texture GL_AMD_vertex_shader_viewport_index GL_AMD_vertex_shader_layer GL_ARB_arrays_of_arrays GL_ARB_base_instance GL_ARB_bindless_texture GL_ARB_blend_func_extended GL_ARB_buffer_storage GL_ARB_clear_buffer_object GL_ARB_clear_texture GL_ARB_clip_control GL_ARB_color_buffer_float GL_ARB_compatibility GL_ARB_compressed_texture_pixel_storage GL_ARB_conservative_depth GL_ARB_compute_shader GL_ARB_compute_variable_group_size GL_ARB_conditional_render_inverted GL_ARB_copy_buffer GL_ARB_copy_image GL_ARB_cull_distance GL_ARB_debug_output GL_ARB_depth_buffer_float GL_ARB_depth_clamp GL_ARB_depth_texture GL_ARB_derivative_control GL_ARB_direct_state_access GL_ARB_draw_buffers GL_ARB_draw_buffers_blend GL_ARB_draw_indirect GL_ARB_draw_elements_base_vertex GL_ARB_draw_instanced GL_ARB_enhanced_layouts GL_ARB_ES2_compatibility GL_ARB_ES3_compatibility GL_ARB_ES3_1_compatibility GL_ARB_ES3_2_compatibility GL_ARB_explicit_attrib_location GL_ARB_explicit_uniform_location GL_ARB_fragment_coord_conventions GL_ARB_fragment_layer_viewport GL_ARB_fragment_program GL_ARB_fragment_program_shadow GL_ARB_fragment_shader GL_ARB_fragment_shader_interlock GL_ARB_framebuffer_no_attachments GL_ARB_framebuffer_object GL_ARB_framebuffer_sRGB GL_ARB_geometry_shader4 GL_ARB_get_program_binary GL_ARB_get_texture_sub_image GL_ARB_gpu_shader5 GL_ARB_gpu_shader_fp64 GL_ARB_gpu_shader_int64 GL_ARB_half_float_pixel GL_ARB_half_float_vertex GL_ARB_imaging GL_ARB_indirect_parameters GL_ARB_instanced_arrays GL_ARB_internalformat_query GL_ARB_internalformat_query2 GL_ARB_invalidate_subdata GL_ARB_map_buffer_alignment GL_ARB_map_buffer_range GL_ARB_multi_bind GL_ARB_multi_draw_indirect GL_ARB_multisample GL_ARB_multitexture GL_ARB_occlusion_query GL_ARB_occlusion_query2 GL_ARB_parallel_shader_compile GL_ARB_pipeline_statistics_query GL_ARB_pixel_buffer_object GL_ARB_point_parameters GL_ARB_point_sprite GL_ARB_post_depth_coverage GL_ARB_program_interface_query GL_ARB_provoking_vertex GL_ARB_query_buffer_object GL_ARB_robust_buffer_access_behavior GL_ARB_robustness GL_ARB_sample_locations GL_ARB_sample_shading GL_ARB_sampler_objects GL_ARB_seamless_cube_map GL_ARB_seamless_cubemap_per_texture GL_ARB_separate_shader_objects GL_ARB_shader_atomic_counter_ops GL_ARB_shader_atomic_counters GL_ARB_shader_ballot GL_ARB_shader_bit_encoding GL_ARB_shader_clock GL_ARB_shader_draw_parameters GL_ARB_shader_group_vote GL_ARB_shader_image_load_store GL_ARB_shader_image_size GL_ARB_shader_objects GL_ARB_shader_precision GL_ARB_shader_storage_buffer_object GL_ARB_shader_subroutine GL_ARB_shader_texture_image_samples GL_ARB_shader_texture_lod GL_ARB_shading_language_100 GL_ARB_shader_viewport_layer_array GL_ARB_shading_language_420pack GL_ARB_shading_language_include GL_ARB_shading_language_packing GL_ARB_shadow GL_ARB_sparse_buffer GL_ARB_sparse_texture GL_ARB_sparse_texture2 GL_ARB_sparse_texture_clamp GL_ARB_stencil_texturing GL_ARB_sync GL_ARB_tessellation_shader GL_ARB_texture_barrier GL_ARB_texture_border_clamp GL_ARB_texture_buffer_object GL_ARB_texture_buffer_object_rgb32 GL_ARB_texture_buffer_range GL_ARB_texture_compression GL_ARB_texture_compression_bptc GL_ARB_texture_compression_rgtc GL_ARB_texture_cube_map GL_ARB_texture_cube_map_array GL_ARB_texture_env_add GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_ARB_texture_filter_minmax GL_ARB_texture_float GL_ARB_texture_gather GL_ARB_texture_mirror_clamp_to_edge GL_ARB_texture_mirrored_repeat GL_ARB_texture_multisample GL_ARB_texture_non_power_of_two GL_ARB_texture_query_levels GL_ARB_texture_query_lod GL_ARB_texture_rectangle GL_ARB_texture_rg GL_ARB_texture_rgb10_a2ui GL_ARB_texture_stencil8 GL_ARB_texture_storage GL_ARB_texture_storage_multisample GL_ARB_texture_swizzle GL_ARB_texture_view GL_ARB_timer_query GL_ARB_transform_feedback2 GL_ARB_transform_feedback3 GL_ARB_transform_feedback_instanced GL_ARB_transform_feedback_overflow_query GL_ARB_transpose_matrix GL_ARB_uniform_buffer_object GL_ARB_vertex_array_bgra GL_ARB_vertex_array_object GL_ARB_vertex_attrib_64bit GL_ARB_vertex_attrib_binding GL_ARB_vertex_buffer_object GL_ARB_vertex_program GL_ARB_vertex_shader GL_ARB_vertex_type_10f_11f_11f_rev GL_ARB_vertex_type_2_10_10_10_rev GL_ARB_viewport_array GL_ARB_window_pos GL_ATI_draw_buffers GL_ATI_texture_float GL_ATI_texture_mirror_once GL_S3_s3tc GL_EXT_texture_env_add GL_EXT_abgr GL_EXT_bgra GL_EXT_bindable_uniform GL_EXT_blend_color GL_EXT_blend_equation_separate GL_EXT_blend_func_separate GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_compiled_vertex_array GL_EXT_Cg_shader GL_EXT_depth_bounds_test GL_EXT_direct_state_access GL_EXT_draw_buffers2 GL_EXT_draw_instanced GL_EXT_draw_range_elements GL_EXT_fog_coord GL_EXT_framebuffer_blit GL_EXT_framebuffer_multisample GL_EXTX_framebuffer_mixed_formats GL_EXT_framebuffer_multisample_blit_scaled GL_EXT_framebuffer_object GL_EXT_framebuffer_sRGB GL_EXT_geometry_shader4 GL_EXT_gpu_program_parameters GL_EXT_gpu_shader4 GL_EXT_multi_draw_arrays GL_EXT_packed_depth_stencil GL_EXT_packed_float GL_EXT_packed_pixels GL_EXT_pixel_buffer_object GL_EXT_point_parameters GL_EXT_polygon_offset_clamp GL_EXT_post_depth_coverage GL_EXT_provoking_vertex GL_EXT_raster_multisample GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_separate_shader_objects GL_EXT_separate_specular_color GL_EXT_shader_image_load_formatted GL_EXT_shader_image_load_store GL_EXT_shader_integer_mix GL_EXT_shadow_funcs GL_EXT_sparse_texture2 GL_EXT_stencil_two_side GL_EXT_stencil_wrap GL_EXT_texture3D GL_EXT_texture_array GL_EXT_texture_buffer_object GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_latc GL_EXT_texture_compression_rgtc GL_EXT_texture_compression_s3tc GL_EXT_texture_cube_map GL_EXT_texture_edge_clamp GL_EXT_texture_env_combine GL_EXT_texture_env_dot3 GL_EXT_texture_filter_anisotropic GL_EXT_texture_filter_minmax GL_EXT_texture_integer GL_EXT_texture_lod GL_EXT_texture_lod_bias GL_EXT_texture_mirror_clamp GL_EXT_texture_object GL_EXT_texture_shared_exponent GL_EXT_texture_sRGB GL_EXT_texture_sRGB_decode GL_EXT_texture_storage GL_EXT_texture_swizzle GL_EXT_timer_query GL_EXT_transform_feedback2 GL_EXT_vertex_array GL_EXT_vertex_array_bgra GL_EXT_vertex_attrib_64bit GL_EXT_import_sync_object GL_IBM_rasterpos_clip GL_IBM_texture_mirrored_repeat GL_KHR_context_flush_control GL_KHR_debug GL_KHR_no_error GL_KHR_robust_buffer_access_behavior GL_KHR_robustness GL_KTX_buffer_region GL_NV_bindless_multi_draw_indirect GL_NV_bindless_multi_draw_indirect_count GL_NV_bindless_texture GL_NV_blend_equation_advanced GL_NV_blend_equation_advanced_coherent GL_NV_blend_square GL_NV_command_list GL_NV_compute_program5 GL_NV_conditional_render GL_NV_conservative_raster GL_NV_conservative_raster_dilate GL_NV_copy_depth_to_color GL_NV_copy_image GL_NV_depth_buffer_float GL_NV_depth_clamp GL_NV_draw_texture GL_NV_ES1_1_compatibility GL_NV_ES3_1_compatibility GL_NV_explicit_multisample GL_NV_fence GL_NV_fill_rectangle GL_NV_float_buffer GL_NV_fog_distance GL_NV_fragment_coverage_to_color GL_NV_fragment_program GL_NV_fragment_program_option GL_NV_fragment_program2 GL_NV_fragment_shader_interlock GL_NV_framebuffer_mixed_samples GL_NV_framebuffer_multisample_coverage GL_NV_geometry_shader4 GL_NV_geometry_shader_passthrough GL_NV_gpu_program4 GL_NV_internalformat_sample_query GL_NV_gpu_program4_1 GL_NV_gpu_program5 GL_NV_gpu_program5_mem_extended GL_NV_gpu_program_fp64 GL_NV_gpu_shader5 GL_NV_half_float GL_NV_light_max_exponent GL_NV_multisample_coverage GL_NV_multisample_filter_hint GL_NV_occlusion_query GL_NV_packed_depth_stencil GL_NV_parameter_buffer_object GL_NV_parameter_buffer_object2 GL_NV_path_rendering GL_NV_path_rendering_shared_edge GL_NV_pixel_data_range GL_NV_point_sprite GL_NV_primitive_restart GL_NV_register_combiners GL_NV_register_combiners2 GL_NV_sample_locations GL_NV_sample_mask_override_coverage GL_NV_shader_atomic_counters GL_NV_shader_atomic_float GL_NV_shader_atomic_fp16_vector GL_NV_shader_atomic_int64 GL_NV_shader_buffer_load GL_NV_shader_storage_buffer_object GL_NV_texgen_reflection GL_NV_texture_barrier GL_NV_texture_compression_vtc GL_NV_texture_env_combine4 GL_NV_texture_multisample GL_NV_texture_rectangle GL_NV_texture_shader GL_NV_texture_shader2 GL_NV_texture_shader3 GL_NV_transform_feedback GL_NV_transform_feedback2 GL_NV_uniform_buffer_unified_memory GL_NV_vertex_array_range GL_NV_vertex_array_range2 GL_NV_vertex_attrib_integer_64bit GL_NV_vertex_buffer_unified_memory GL_NV_vertex_program GL_NV_vertex_program1_1 GL_NV_vertex_program2 GL_NV_vertex_program2_option GL_NV_vertex_program3 GL_NV_viewport_array2 GL_NVX_conditional_render GL_NVX_gpu_memory_info GL_NVX_nvenc_interop GL_NV_shader_thread_group GL_NV_shader_thread_shuffle GL_KHR_blend_equation_advanced GL_KHR_blend_equation_advanced_coherent GL_SGIS_generate_mipmap GL_SGIS_texture_lod GL_SGIX_depth_texture GL_SGIX_shadow GL_SUN_slice_accum GL_WIN_swap_hint WGL_EXT_swap_control 

150 Messages

 • 

2.9K Points

I have the same problem similar spec and stronger GPU but I also have bigger files 80MP. I have to restart lightroom every 10-15 images to get the performance back up again an I can see the lightroom background task reducing the memory for about 10 seconds until it close completely  and only then I can restart it.

87 Messages

 • 

1.6K Points

There's no need for restarting LR. Minimize it, wait 5 to 10 seconds, maximize it, done. And do it again every few pictures.
Best solution: Go back to LR CC 2015.5.1 and have a closer look at what Capture One or DXO does.

26 Messages

 • 

350 Points

5 years ago

Hello
I guess that we are getting the idea that quadrupling the files sizes that Lightroom has to deal with almost overnight, is placing a great strain on its architecture. Processing 1:1 previews at standard HD is fine, 4k previews for super HD are bringing very powerful computers to their knees. It has to be worse for laptops as the CPUs shut down as they overheat, or if they are using just battery power. Workstations can turn the fans on and deal with the heat that way, but in the end the CPUs have thermal protection and will in the end shut down. Restarting or resting Lightroom, brings some thermal relief.

MDE

82 Messages

 • 

1.3K Points

If you ask me: LR main backbone and the local adjustments (that counts for spot removal too) need complete re-writing.

Usage of GPU goes to 0. It is used for above FullHD.

What about GPU utilization aside from the visualization? Had anyone even experimented?