Lightroom 2015.6 Extremely Slow

  • 43
  • Problem
  • Updated 3 years ago

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.

Photo of Jerry Syder

Jerry Syder

  • 367 Posts
  • 170 Reply Likes

Posted 3 years ago

  • 43
Photo of Hayley Green

Hayley Green

  • 2 Posts
  • 0 Reply Likes
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!
(Edited)
Photo of Mike Engles

Mike Engles

  • 26 Posts
  • 2 Reply Likes

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

Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1681 Posts
  • 577 Reply Likes
> "quite a lot of cloning"
This is known to be very taxing to Lightroom, especially if you have a lot of them.
(Edited)
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1681 Posts
  • 577 Reply Likes
@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?
Photo of Mike Engles

Mike Engles

  • 26 Posts
  • 2 Reply Likes

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

(Edited)
Photo of Kostadin Luchansky

Kostadin Luchansky

  • 22 Posts
  • 5 Reply Likes
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.
Photo of David Efurd

David Efurd

  • 13 Posts
  • 5 Reply Likes
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. 
Photo of Assaf Frank

Assaf Frank

  • 148 Posts
  • 46 Reply Likes
same here
Photo of Mike Engles

Mike Engles

  • 26 Posts
  • 2 Reply Likes

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

Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1681 Posts
  • 577 Reply Likes
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.
Photo of Mike Engles

Mike Engles

  • 26 Posts
  • 2 Reply Likes

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

Photo of Mike Engles

Mike Engles

  • 26 Posts
  • 2 Reply Likes

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


(Edited)
Photo of Gethin

Gethin

  • 47 Posts
  • 7 Reply Likes
@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 
Photo of Assaf Frank

Assaf Frank

  • 148 Posts
  • 46 Reply Likes
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.
(Edited)
Photo of Stefan Redel

Stefan Redel

  • 88 Posts
  • 30 Reply Likes
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.
Photo of Mike Engles

Mike Engles

  • 26 Posts
  • 2 Reply Likes

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

(Edited)
Photo of Diko

Diko

  • 79 Posts
  • 12 Reply Likes
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?
(Edited)
Photo of megohms

megohms

  • 1 Post
  • 1 Reply Like

Minimizing, Restarting, Resetting, Rebooting, Uninstall, Reinstall, Turning this off, Turning that on, What is your system info, what CPU do you have, are you MAC or Windows.  

I don’t get it! This should work correctly right out of the gate! 

Maybe I missed it but has Adobe even acknowledged there is a problem with this latest update and are they working on a solution?

 Or are they going to tell us to dial this toll free number: 1-800-WHA-AAAA!

Photo of Stefan Redel

Stefan Redel

  • 88 Posts
  • 30 Reply Likes

Nope. Not acknowledged from Adobe. As always.

Photo of Jerry Syder

Jerry Syder

  • 337 Posts
  • 152 Reply Likes
Trust us - we feel your pain @megohms
Photo of David Collins

David Collins

  • 6 Posts
  • 3 Reply Likes
Way too long for Adobe to have not acknowledged the pain everyone is having with 2015.6. I've gone back to 2015.5.1 and all is ok again
Photo of Todd Kough

Todd Kough

  • 2 Posts
  • 2 Reply Likes
This reply was created from a merged topic originally titled Is anyone else haing issues with lightroom running much slower after the recent u....

Is anyone else haing issues with lightroom running much slower after the recent update? Have cleared cache, optimized catalog, defragmented drives, and move scratch to different drive. Still running slow 2-3 sec delay between image switch (import with 1:1) and selecting tools had about a 2 sec delay.
Photo of Gethin

Gethin

  • 47 Posts
  • 7 Reply Likes
@Simon
This has nothing to do with cloning. Not a thing.  I gave up on cloning anything but the odd dust spot a long time ago.  Just reduces lightroom to a crawl.  Also my workflow has the detail and noise adjustments off until just before export.

To hear there wont be a quick fix is dismal.  At the moment there are people willing to help, but if days go by with no response I for one will revert to a previous version, or try to find an alternative (and if I go there then I may as well ditch the whole suite).

So here we are. What do you need to know? Would screen-captures be helpful? 
Photo of David Efurd

David Efurd

  • 13 Posts
  • 5 Reply Likes
Yeah it seems like I've had to adjust my workflow after each significant release of LR to keep working until a patch release becomes available to address performance issues. I'm now actually at a point where all I pretty much do in LR now is cull images, rate them, etc. and VERY basic tone adjustments and everything else I have to do in PS. Such a shame because they keep enhancing LR and adding cool features but I can't use them and still stay productive (or keep my sanity).
Photo of Assaf Frank

Assaf Frank

  • 148 Posts
  • 46 Reply Likes
have you thought using capture one?
Photo of David Efurd

David Efurd

  • 13 Posts
  • 5 Reply Likes
Yes, definitely. I've been wanting to try it out for a while now because I've heard it's much better at tethering (at least for Sony cameras) than LR but the thought of switching over is daunting because I've spent so much time perfecting my workflow using LR but it's getting to a point where I might not have a choice.
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1681 Posts
  • 577 Reply Likes
@Gethin
Thank you. A screen record of what you do in Lightroom that slows you down would be helpful. Description of your system setup is helpful (i.e. Lightroom Help>System Info...). 
Photo of Gethin

Gethin

  • 47 Posts
  • 7 Reply Likes
Hi Simon, yes did that, Its up there ^ :)
I will do screen cap soon
Photo of Denis Jobst

Denis Jobst

  • 1 Post
  • 1 Reply Like
Have the same problems here. If i use LR nothing works on my mac anymore. I noticed it as i used the healing brush tool in PS (which is slower even). LR + Healing Brush in PS = Mac freeze. After that i looked at the activity monitor and saw this huge CPU usage of LR.
Everytime since the last 3 years Adobe updated LR or PS some big issues occur.
Photo of Mike Engles

Mike Engles

  • 26 Posts
  • 2 Reply Likes

Hello

If you like Lightroom History, then I have just found out that Capture One does not have a history, but seems to have all other major Lightroom features. You can also subscribe for 3 months at a time, for an extended trial.

MDE

Photo of David Efurd

David Efurd

  • 13 Posts
  • 5 Reply Likes
That's a bummer.  I definitely use the history quite a bit.  Does it have an integration with external editors like Photoshop.  I definitely like that integration between LR and PS where I can just choose Edit and it opens up in PS and then upon Save/Close it comes right back into LR for final touches and export.  I'll have to give Capture One a trial run and see how it works.  Thanks for the info!
Photo of Mike Engles

Mike Engles

  • 26 Posts
  • 2 Reply Likes

Hello

It will open stuff in Photoshop but does not return back.Also not having a history, might give a bit of a clue as to why it works so efficiently.

The way it does clones and adjustments as separately listed layers, is exactly how Lightroom should work.

It does look like a very capable programme. I have only looked at Youtube videos. I have downloaded Capture One, but am wary of installing stuff, till I know more.

MDE

Photo of Diko

Diko

  • 79 Posts
  • 12 Reply Likes
C1 has sharper rendering of RAW files as well. Why and how - don't know.
Photo of Beverly Parks

Beverly Parks

  • 62 Posts
  • 11 Reply Likes
Lightroom 6.6 standalone.  Kept getting slower and slower.  Weird things started happening, like progress bar not clearing from the screen after the process (HDR merge) finished (posted about that in new thread this morning) and telling me I had two Lightroom processes going at the same time (but I didn't).

Just tried to print something from a web page in Firefox and got the message that there was not enough memory to print.  First time I've ever encountered that!  Closed Lightroom and it printed fine.
Photo of Chris Pedersen

Chris Pedersen

  • 5 Posts
  • 0 Reply Likes
I can't help wondering, if we, the users of this forum are just a small unlucky percentage of a lot of satisfied users?

Is anyone not having these slowness issues in LR 6.6?
Or do you know someone, for who its running smoothly?
Photo of Mike Engles

Mike Engles

  • 26 Posts
  • 2 Reply Likes

Hello Simon

6 days ago I posted 3 Sys infos, which indicate that Lightroom seems to use virtual memory, rather than real memory.

"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"

What kind of memory are the virtual memory and memory cache?

Is there some sort of limit on how much real memory Lightroom can use?

MDE

Photo of Mike Engles

Mike Engles

  • 26 Posts
  • 2 Reply Likes

Hello

OK here are some numbers for my system

Home built i7 Quadcore 870 2.93gHz 16gb ram Samsung 850 SSD.

AMD HD 5450 video System is 6 years old

100 images on a normal hard drive.

 Made a new catalogue.

Time to make 100 1920x1200 previews

Adjusted 1 image exposure, curves, lens correction profile, detail, noise and calibration. Applied to all thumbnails.

Clicked on  images at 100% zoom, timed redraw

Made 6 Random clones 100, 43,100, zoomed 100% and panned randomly timed redraw

Results

Lightroom 6

Preview build time 7m 40s

Apply correction to thumbnails, instant

Clicked zoom 100% redraw 5s average

6 random clones 100% random panning, redraw within a sec, panning smooth

Lightroom 6.3

Preview Build time 7m20s

Apply correction to thumbnails, instant

Clicked zoom 100% redraw 5s average

6 random clones 100% random panning, redraw within a sec, panning smooth

Lightroom 6.6

Preview Build time 7m50s

Apply correction to thumbnails, instant

Clicked zoom 100% redraw 6s average, sometimes would not respond to clicking on another image.

6 random clones 100% random panning, redraw within a sec, panning smooth, just sometimes would go notchy.

I conclude that on my system, there is not much in it, but Lightroom 6.6 is a mite less responsive, than previous versions.

MDE




(Edited)
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1681 Posts
  • 577 Reply Likes
Thanks Mike for you data point. For your system configuration, I don't expect the other performance improvement that we made in Lr CC 2015.6/6.6, such as the improved walking photos performance in develop (which does use a little bit more RAM, but your 16GB of RAM is fine), would adversely affect you.

Your "zoom into 100%" test is in the library module or the develop?

On your virtual memory usage question, Lightroom could use up-to 50% of the total RAM for image processing (heavy lifting part). We're investing Lightroom's other use of the memory (for the UI and glue code etc).
Photo of Mike Engles

Mike Engles

  • 26 Posts
  • 2 Reply Likes

Hello Simon

All tests are in Develop, I only go to Library for import and changing folders.

For import, I always copy files to a folder on the hard drive and then import into Lightroom, so Preview building starts when the import button is pressed.

Is cache memory SSD memory or real ram?

MDE


Photo of Gethin

Gethin

  • 47 Posts
  • 7 Reply Likes
Zoom in to 100% can take 15+ seconds on my system.  (i7 5820 @3.8 Ghz, 64 gb ram, gtx970 (not used)  4gb, raid 5 HDD, cat on NVME ssd, ssd system drive)
Photo of m sadat

m sadat

  • 16 Posts
  • 9 Reply Likes
my guess is this code base for adobe has ran its course and this is the best it can do till they move to a new base, it will be shitty .i also think they have started the to work on the next generation of their codebase but when we get it, i don't know. as of right now lr is inadequate to handle today's cameras which keep getting bigger sensors. i think its time to move on and find alternatives, i will take a look @ aftershot pro and capture one, though i hate to learn another tool but there is no choice.
Photo of Assaf Frank

Assaf Frank

  • 148 Posts
  • 46 Reply Likes
Capture one is amazing in terms of raw processing by far superior to lightroom. The only issue i have with it is that my work flow has been built around lightroom in the last 8 years and I can't get my head around doing the switch. C1 has progressed allot in the last 2 years and if i had to start today I won't think twice. If your workflow is pretty straight forward and you dont use too many plugins you may want to give C1 a go.
Photo of Gordon Betsill

Gordon Betsill

  • 12 Posts
  • 0 Reply Likes
Assaf, does Capture 1 have a skin smoother and all that goes along with making a model's face eyes, and skin look good, or, I should say, better than it actually is?
Thanks!
Photo of Mike Engles

Mike Engles

  • 26 Posts
  • 2 Reply Likes

Hello

If you like the History in Lightroom, then as far as I know Capture One does not keepa History

MDE


Photo of Gordon Betsill

Gordon Betsill

  • 12 Posts
  • 0 Reply Likes
Before I had a computer crash, I was using LR5 with no problems.  As soon as I get my computer back I had full intentions of upgrading to 6.6, but after reading all of these problems with 6.6 I'm having a major 're-thinking' of upgrading.  The main reason that I wanted the newer version was because of the new 'HAZE' feature.  I'm now wondering if it's even worth all that you people are going thru.
Just one question:  would any of you consider going back to 5 or are you happy with 6.5?
Thanks so much for your consideration.
(Edited)
Photo of Stefan Redel

Stefan Redel

  • 88 Posts
  • 29 Reply Likes
The Haze-feature is not available at 6. Only at CC.
But... Someone with CC can make you presets with several Haze-settings. That ones you can use then on 6.
Photo of Gordon Betsill

Gordon Betsill

  • 12 Posts
  • 0 Reply Likes
Stefan, well, what a shocker.  I thought the haze came with any version of 6.  Thanks so much for informing me.  Since I  don't have that feature to look forward to, I see no need in leaving 5.  I cannot tell you how much I appreciate you informing me of this; you're a great help and have solved a major decision for me.

Have a great holiday!
Photo of Gordon Betsill

Gordon Betsill

  • 12 Posts
  • 0 Reply Likes
What in the heck is going on with Adobe?  As I said before the reason I was upgrading was to get the new HAZE feature.  Now, I learn it's only available thru CC.  How fair is that?  That was really the ONLY seemingly important upgrade in 6. 
All of you people who clearly know programs and computers well, I extend a sincere thank you for your knowledge and willingness to share.  If I had gone to the expense and trouble to upgrade and then to realize there was no HAZE feature which was heavily advertised when 6 was first released, I'd have been PO'd and I don't like having strong negative emotions.  I have had PSP for years and never had this type problem.  Of course, it cannot compare to LR when Adobe is on top of things and allows LR to work properly which seems to have become rare.
but it works.
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 5522 Posts
  • 1162 Reply Likes
Gordon, if it has been less than 30 days, you can request a refund of LR 6.x and then subscribe to Lightroom CC2015 and you will get the Dehaze slider and other features that are part of the Creative Cloud version. 
Photo of jeckylproductions

jeckylproductions

  • 8 Posts
  • 3 Reply Likes
Fair statement regarding 6.0 and not getting haze but honestly if you're not taking advantage of CC then you're missing out. The industry as a whole is moving to a subscription model and their will only be features available through the subscription model. I imagine that adobe will not release any further stand alone products in the near future. And at $10 a month for any and all upgrades for PS and LR it's a heck of a lot cheaper tha. Upgrading yearly or even every 2 years.

Thad just my two cents.
Photo of William Sprague

William Sprague

  • 13 Posts
  • 8 Reply Likes
Gordon,

I'm following this topic because I'm interested, not because I am having trouble.  On the contrary, I am one of the thousands (or more) that are not having trouble with slowness.  (I'm on a Windows 10 computer.)  I have sympathy and concern with the hundreds (?) that are having slowness trouble and those trying to fix it.  

Keep LR5.  Try 6.6 or the CC.  My bet is that it will work fine.  If not, get a refund and fall back to LR5.  Note that fewer are having trouble with 6.5.  Some say they are continuing to use that.  Also, be aware that improvements in the Haze tools have come with the CC updates that have not come with the 6.x updates.

Bill
(Edited)
Photo of Gordon Betsill

Gordon Betsill

  • 12 Posts
  • 0 Reply Likes
William, thanks so much for your kindness in taking the time to not only reply but to give some little hints as to what to do,  Not that it matters, but before the crash, I, also, was on W10.
I  cannot do anything until I get back my computer and praying I have some data left on it.  Since I'm a photographer, it's the pics or the lack thereof that concern me the most. 
Have a great 4th!
Photo of Jeff Harmon

Jeff Harmon

  • 51 Posts
  • 45 Reply Likes
Not that it should take this to make it work, but I have recently discovered that if you make Lightroom actually use the Smart Previews everything is MUCH faster.  You sort of have to hack Lightroom to make it work, but I have found it to increase the speed of everything by about 4x.  Here is how to hack Lightroom to make it work:

1) Import your photos, make sure to check the box "Build Smart Previews".  Yes, this is going to make a process that is already more slow than it should be take even longer, but it will reduce frustration later.
2) Go to the file system on your computer (Windows Explorer on Windows, Finder in macOS), and rename the folder where the original files are located.  This is a temporary thing so I just add the word "temp" on the end of the folder name.
3) Now Lightroom doesn't know where to find the original files and is forced to use the Smart Previews instead!  You will notice that just under the Histogram it now says "Smart Preview" alone instead of "Original + Smart Preview".  With Lightroom using the Smart Preview that is significantly smaller in file size than the original (at least with RAW files) all of the sliders and tools work significantly faster.  
4)  Do your culling and a lot of editing at much faster speeds (like 4x faster!)
5)  If you need to roundtrip a photo into Photoshop and/or export, go back out to the file system (Windows Explorer or Finder) and change the name back to what Lightroom is expecting.

Adobe, would love to see a checkbox somewhere to have Develop use the Smart Preview instead of the Original even though it is available for everything it can so that I don't have to do the folder rename hack.
Photo of David Efurd

David Efurd

  • 13 Posts
  • 5 Reply Likes
Yeah it would be very nice to see an option built into LR to allow the end-user the choice to use Smart Previews rather than it determining when they should be used for us. I think it's a design flaw to assume the only time we'd ever want to use Smart Previews is when the original files are inaccessible because they're on a disconnected external drive. It's a significant performance boost using the SP's and should be up to the user to decide when to use them. I realize there are some limitations when using them, but for the vast majority of the time, I could easily get by using them and my workflow would be incredibly faster. I would definitely use them after every patch upgrade Adobe releases for the product. :)
Photo of Robert Frost

Robert Frost

  • 426 Posts
  • 73 Reply Likes

But if you use Smart Previews for your culling, the original files don't get deleted, do they?


Bob frost

Photo of Jeff Harmon

Jeff Harmon

  • 51 Posts
  • 45 Reply Likes
If you delete them with only Smart Previews, you are right, the photos won't be deleted from your hard drive.  They will only be removed from the catalog.  So, instead just mark those that you want to delete as rejected (use the "x" key).  Then when you are done culling, maybe even done doing most of your edits, rename the folder back to the original name where Lightroom is expecting them to be and filter down to those that have been flagged as rejected to select and delete them.

More work for sure, which is why I think Adobe should add a checkbox to preferences where Smart Previews will be used over the original files for culling and editing, only switching to the originals for those few functions where they are needed like deleting photos or round-tripping to Photoshop.
Photo of Diko

Diko

  • 78 Posts
  • 12 Reply Likes
Currently culling using the FastRAW Viewer. So much faster and better. ;-) And cheaper. And more flexible. They already display the Canon 5D Mark IV ;-)
Photo of David Collins

David Collins

  • 6 Posts
  • 3 Reply Likes
So has Adobe released anything official about this performance problem so many people are having?  

With so many people having issues, surely they cant be silent on this? 
Photo of Gordon Betsill

Gordon Betsill

  • 12 Posts
  • 0 Reply Likes
Watch them!
Photo of Ruth O'Leary

Ruth O'Leary

  • 2 Posts
  • 0 Reply Likes
I upgraded to 2015.6 a few days ago. Today I no longer get a preview when I import files. I still have previews for previous imports, just not on my new ones. I haven't been able to get any work done today. I've restarted, turned off the graphics button, reinstalled ... still no previews. I can't go back to a previous version because my catalog is too new now. Furious doesn't come close.
Photo of jeckylproductions

jeckylproductions

  • 8 Posts
  • 3 Reply Likes
Here's what you can do. Uninstall 2015.6, it was useless for me no matter what I tried.

Use this link to download the 6.0 base unless you still have it around, it's 700mb or so I can't remember. http://prodesigntools.com/trials3/Ado...

After 6.0 is installed use this Link to download 2015.5.1 it was the version just before 2015.6 so your catalogs will have no issues opening. http://prodesigntools.com/swupdl/upda...

Until a new version becomes available I'm sticking with 2015.5.1, hope this works for you!

By the way, the links are safe I've used them and Adobe was the one that referred me to the above site for older full versions since adobe no longer has them available for public to easily downlod but these links download directly from adobes servers I'm told.
Photo of Ruth O'Leary

Ruth O'Leary

  • 2 Posts
  • 0 Reply Likes
I optimised the catalog and went out for a few hours. When I restarted LR was working properly again. Weird.
Photo of Neil Shapiro

Neil Shapiro

  • 10 Posts
  • 8 Reply Likes
Finally could not take it anymore...I reverted to the prior 2015.5.1 version via the instructions here and LR is usable again.  Adobe...you need to get off your XXX and fix this!
Photo of Assaf Frank

Assaf Frank

  • 148 Posts
  • 46 Reply Likes
If you are using 4K display and having slow response and memory leaks try and reduce the resolution to 1920x1080. Everything will get much faster and more responsive. I would expect adobe to acknowledge they have a performance issue with 4K and are working on a fix and not leave us hanging to dry...
Photo of Robert Routson

Robert Routson

  • 3 Posts
  • 0 Reply Likes
Lol lightroom is made to batch edit. 50 photos at a time all day long. Absolutely there is going to be a several second pause. But it shouldnt continue to eat up resources and cause the entire system to slow to a crawl and crash. I dont even understand how that is a response. If you google lightroom cc 2015 ram memory over usage or lightroom cc 2015 system crash youll get 20 or 30 threads right off the get go on this same issue. Macs are having the same problems that PCs are having. This is not a hardware issue, this is a software issue with Adobes released program. The nice thing about being such a big company is that you dont have to test your software all the way through, you can release it and let the users find the bugs for you. In the mean time were stuck with what we have. So keep filing the error reports with Adobe and patiently wait for them to come around fix this horrendous problem...
The sad part is that we keep thinking that its something we did. After we put so much money into our systems to ensure that they are running top notch hardware the bottleneck ends up being the software. Of course theyre aware of the problem, theyre just trying to figure out how to release an update and not look like goobers doing it. All of the tech guys that keep posting and saying theyre trying to help us absolutely know what is going on ... theyre just holding our hands getting us too look in a different direction while Adobe pulls its pants back up. Lol if you google the threads for this problem there are multiple Adobe reps repeating the exact same thing and everyone is having the same problems. Do you think for a second that the company doesnt know what is going on ...
Photo of Robert Routson

Robert Routson

  • 3 Posts
  • 0 Reply Likes
Photo of Assaf Frank

Assaf Frank

  • 148 Posts
  • 46 Reply Likes
Good News - this issue has been fixed in 2015.6.1 just worked with it for about 20 minutes and it is looking good. thank you adobe!
http://blogs.adobe.com/lightroomjournal/2016/07/lightroom-cc-2015-6-1-now-available.html
Photo of peter bertilsson

peter bertilsson

  • 3 Posts
  • 3 Reply Likes
Still on CC. Still slow. Seems to me that LR cant use more than 6-7 GB of RAM. Every time it gets up there it slows. I shut down LR and start up again and its fine, until....
BTW, I have 64 GB installed so plenty left but LR is not using it!
Photo of Stefan Redel

Stefan Redel

  • 88 Posts
  • 30 Reply Likes
I second that. Have 32 Gig installed, LR doesn't make use of it and gets slow after a time.
Photo of Chris Pedersen

Chris Pedersen

  • 5 Posts
  • 0 Reply Likes
Same issue here...
Photo of jeckylproductions

jeckylproductions

  • 8 Posts
  • 3 Reply Likes
For the last several months I have gone back and forth between versions.  Today I updated my Nvidia GFX card driver to the latest 375.86.  I have noticed a significant improvement in LR 2015.7

I know its not the end all to the performance problems I've been plagued with LR but it is a start to a bit more reasonable workflow.
Photo of Mihael Tominšek

Mihael Tominšek

  • 37 Posts
  • 31 Reply Likes
With Lr it seems there is improvement every time you do something to system. So Upgrading driver seems the same. But problem is any speed improvement is only temporarily. Let say I switched to Smart Previews - WOW what a smooth work. But only for 2/3 of the project. Rest of it and any nex projects are doomed again. Than Driver... nice improvement, but for a day. Restarting Lr... for na hour. Restarting PC, same. NOT USING Lr for a day or two yields few hours hassle free work. Seriously!

What the heck is going on here. Are Lr get fatique?  Every time I not use Lr for longer period it is smooth as butter for few hours or even whole day. Than it "fills up" something and is slow as bone growth again. I have 99GB of cache already. On separate SSD!