• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

Lightroom CC 2015.7 slower than death >:(

New Here ,
Sep 21, 2016 Sep 21, 2016

Copy link to clipboard

Copied

FOR THE LOVE OF GOD PLEASE HELP ME.

I've been using Lightroom since before the CC days and have always been very happy with the program until recently. While I fully understand that the program is progressing quite quickly and could potentially render some computers obsolete for the newer versions of the program, I don't believe that this could or should be the case for why LR is running so poorly. Following the previous update I was encountering intermittent moments of extreme bog down in the program that I was hoping would be fixed by the most recent update, but have thus far only encountered a further lack of usability. LR is struggling to import batches of photos, giving me the spinning ball of death when I simply try to access menus, taking no less than 4-5 seconds to switch between photos, and the same time over again to respond to any of the editing sliders, presets, etc., giving me the spinning ball of death or crashing often times when I try to enter into the develop module, god forbid I'd want the luxury of switching between photos within the develop module instead of the library!

In short, LR is downright not useable.

I'm no computer genius, but these are things I've done as of now:

- I have turned off the Graphics Processor

- Dropped JPEG preview sizes in general

- In Catalog settings I have lowered both preview size and quality to the minimum

- Have increased my Camera Raw Cache settings to 70gb (which seems ridiculous)

- Have Optimized my Catalogs

Things I have not done:

- Turned off Sharpen, Lens Correction, Noise reduction for every photo (because I think this is absolutely ridiculous)

- Consolidated all of my catalogs

- Shrunk folder sizes

While I've heard that these last items can sometimes help, I refuse to pay monthly for a program that is going subject me to the rage of such tedium, and I refuse to believe that Adobe is that irresponsible that they would make this program so power hungry and memory intensive that it would be too hip for a 1 year old computer.

To either adobe or some interweb white knight, please help me make my photos sparkly and pretty before I set my computer on fire and throw an adult temper tantrum. I'd be eternally grateful for any help.

I'm currently working on a mid 2015 15inch Macbook Pro Retina with all of the system specs listed down below.

Lightroom version: CC 2015.7 [ 1090788 ]

License: Creative Cloud

Operating system: Mac OS 10

Version: 10.11 [6]

Application architecture: x64

Logical processor count: 8

Processor speed: 2.5 GHz

Built-in memory: 16,384.0 MB

Real memory available to Lightroom: 16,384.0 MB

Real memory used by Lightroom: 578.9 MB (3.5%)

Virtual memory used by Lightroom: 994.8 MB

Memory cache size: 96.3 MB

Maximum thread count used by Camera Raw: 8

Camera Raw SIMD optimization: SSE2,AVX,AVX2

Displays: 1) 2880x1800

Graphics Processor Info:

AMD Radeon R9 M370X OpenGL Engine

Check OpenGL support: Passed

Vendor: ATI Technologies Inc.

Version: 4.1 ATI-1.42.15

Renderer: AMD Radeon R9 M370X OpenGL Engine

LanguageVersion: 4.10

Views

15.3K

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Participant ,
Mar 10, 2017 Mar 10, 2017

Copy link to clipboard

Copied

I posted to a new thread.

Slows down over time during session

The problem continues in 2015.9. on the highest-end equipment and all the latest software. Is easily replicated.

For me the slowness creeps in over time: after editing 20 or so photos it becomes noticeable and progressively gets worse. If I let it continue, I start seeing the screen go black on every function.

Quitting and restarting LR resets and starts this all over again.

Windows 10

Intel 6950X

256GB RAM

2/Nvidia Titan Pascals 2/Nvidia GeForce 1080's  (tried with and without acceleration on)

All SSD or M.2 storage

38" LG Superwide Monitor and LG Standard HD TV

Optimized catalog

~10000 image catalog

100GB Cache (purged before testing)

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Participant ,
Mar 13, 2017 Mar 13, 2017

Copy link to clipboard

Copied

I see several folks now reporting that this slowdown issue is related to having multiple cores/CPUs. According to them, the more cores you have the more likely you will see the slowdown. Ugh.

Some testers are limiting LR to 4 cores (in Windows) and reporting success.

Needless to say, this should be a priority fix.

Lance

See:

At wits end with Lightroom's slowness...

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Advocate ,
Mar 13, 2017 Mar 13, 2017

Copy link to clipboard

Copied

I have a shortcut to LR on my desktop, and I altered the 'Target' line to the following. That only allows LR to use 4/8 cores, and the other 2/4 cores of my 6/12 core cpu are just available to the system and other programs.

C:\Windows\System32\cmd.exe /c start  "lightroom" /affinity FF  "C:\Program Files\Adobe\Adobe Lightroom\lightroom.exe"

Take note of the spaces between commands.

Bob Frost

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Participant ,
Mar 14, 2017 Mar 14, 2017

Copy link to clipboard

Copied

Hi Bob,

I tried this idea and confirm that this method does NOT seem to improve my situation.

With testing I still see, even after setting affinity to 4 cores, the same behavior of performance degradation over time during a session.

Thanks,

Lance

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Apr 05, 2017 Apr 05, 2017

Copy link to clipboard

Copied

Yes, no improvement. Still want to jump out my window and just end it all and let the beach balls have their way. Adobe should be refunding subscription money.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Engaged ,
Mar 13, 2017 Mar 13, 2017

Copy link to clipboard

Copied

For what it's worth, version 6.6.1 remains the last LR version that is stable and useful for me. 6.7, 6.8 and 6.9 all have the same issue - they're slow, start to lag more and more as I use them, and I eventually revert to v6.6.1 (2015.6). Something quite significant must have changed "under the hood".

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Mar 17, 2017 Mar 17, 2017

Copy link to clipboard

Copied

The new update did not fix anything regarding the performance speed and stability.

Lightroom is getting more and more useless with every update! I honestly have no idea what the developers at Adobe are doing!!! The app is degrading rather than advancing with every new update, it is ridiculous! I honestly cannot meet deadlines with clients due to its slowness... not only slower than a dying turtle but also it keeps freezing my machine as a whole every time i try to do anything whether in the develop model or  even importing photos in library to the extent that I am forced to either force-quit Lightroom or force-shut the whole computer to get rid of it! That is truly crazy! My computer is not the most recent piece of technology but And I find it ridiculous that in order to use this app I would need to keep investing in a newer more advance machine regularly!

If this continues I am afraid Lightroom will no longer be the program of choice for many professionals who needs their gear, equipments and apps to be reliable every time they need to use them.

What a shame!

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Mar 17, 2017 Mar 17, 2017

Copy link to clipboard

Copied

I now have developed this problem also in the last week and it is very frustrating...  I did a complete reinstall and update to 2015.9 last night and no change.  For me I can't even click the Import button without the system coming to a near complete stop.  Browsing the library is not too bad but once I click import it will freeze up entirely or take minutes to update the options for import, but every click after that the delay gets longer and longer.  At first I thought it was an SD card problem but it hangs even without the card reader attached.  This really snuck up on me in a matter of a few days and now it's basically unusable.  I optimized my catalog, disable all the plug-ins and all the other tips I can find in the forum and still no resolution.

Windows 10 Pro 64 bit

16 GB Ram

Intel i5-3570 3.4

256 GB SSD with multiple secondary disk drives

Lightroom version: CC 2015.9 [ 1106920 ]

License: Creative Cloud

Operating system: Windows 10

Version: 10.0

Application architecture: x64

System architecture: x64

Logical processor count: 4

Processor speed: 3.5 GHz

Built-in memory: 16330.1 MB

Real memory available to Lightroom: 16330.1 MB

Real memory used by Lightroom: 463.5 MB (2.8%)

Virtual memory used by Lightroom: 554.7 MB

GDI objects count: 449

USER objects count: 1149

Process handles count: 1093

Memory cache size: 33.1MB / 3826.5MB (0.9%)

Maximum thread count used by Camera Raw: 4

Camera Raw SIMD optimization: SSE2,AVX

Camera Raw virtual memory: 20MB / 8165MB (0%)

System DPI setting: 96 DPI

Desktop composition enabled: Yes

Displays: 1) 1920x1200

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 376.53

Renderer: GeForce GTX 970/PCIe/SSE2

LanguageVersion: 3.30 NVIDIA via Cg compiler

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

Library Path: E:\hilld\Pictures\Lightroom\Lightroom Catalog.lrcat

Settings Folder: C:\Users\hilld\AppData\Roaming\Adobe\Lightroom

Installed Plugins:

1) Canon Print Studio Pro

2) DxO OpticsPro 11

3) DxO OpticsPro 11 Importer

4) Flickr

5) HDR Efex Pro 2

Config.lua flags: None

Adapter #1: Vendor : 10de

  Device : 13c2

  Subsystem : 31601462

  Revision : a1

  Video Memory : 4058

Adapter #2: Vendor : 1414

  Device : 8c

  Subsystem : 0

  Revision : 0

  Video Memory : 0

AudioDeviceIOBlockSize: 1024

AudioDeviceName: Speakers (Realtek High Definition Audio)

AudioDeviceNumberOfChannels: 2

AudioDeviceSampleRate: 48000

Build: LR5x8

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 376.53

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_gl_spirv 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_window_rectangles 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_alpha_to_coverage_dither_control 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_draw_vulkan_image 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_NV_viewport_swizzle GL_NVX_conditional_render GL_NVX_gpu_memory_info GL_NVX_multigpu_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

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Mar 17, 2017 Mar 17, 2017

Copy link to clipboard

Copied

You don't mention resetting your preferences - a bad preference file will survive an uninstall/reinstall.

Close Lightroom

Hold down [Alt/Opt}+[Shift] while relaunching Lightroom

Overwrite the preferences when prompted.

Close Lightroom.

Reboot.

Do you still have the issue with the hang on import?

Rikk Flohr - Customer Advocacy: Adobe Photography Products

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Mar 17, 2017 Mar 17, 2017

Copy link to clipboard

Copied

Thanks for the suggestion, unfortunately no that did not help.  Still hanging on import.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Mar 17, 2017 Mar 17, 2017

Copy link to clipboard

Copied

Actually I will correct my answer.  I did another reboot and it does seem to be improved now.  Hopefully this is "the fix".  Thanks and I'll report back if there are more problems.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Participant ,
Mar 17, 2017 Mar 17, 2017

Copy link to clipboard

Copied

It would be nice Rikk, if you could acknowledge that you guys are seeing the problem.

Why is there no known issues page for LR like there is for AE and PP?

Lance

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Mar 27, 2017 Mar 27, 2017

Copy link to clipboard

Copied

rlancemoody​ said "It would be nice Rikk, if you could acknowledge that you guys are seeing the problem."

Acknowledgement of issues is posted on the support forum here:

Photoshop Lightroom | Photoshop Family Customer Community

Issues reported on that forum with reproducible steps are marked as Acknowledged.
By setting the search of the forum to "Problems" and then setting the pull-down to "Acknowledged", you can see a list of issues marked by Adobe Staff.  Here is a quick link to the search: Photoshop Lightroom | Photoshop Family Customer Community

If a particular issue doesn't appear in this list, it may not have been posted, or the steps provided may not of have allowed us to reproduce the issue.

Rikk Flohr - Customer Advocacy: Adobe Photography Products

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Participant ,
Mar 27, 2017 Mar 27, 2017

Copy link to clipboard

Copied

Thanks Rikk,

Unfortunately, this procedure doesn't seem to separate issues seen and/or squashed in various versions so it's highly inferior to the current issues pages that are available for After Effects and Premiere.

To add insult to injury, it doesn't appear that this slow down issue has been acknowledged at all, making this 6 months old thread and the offers I and others have made to more fully help document the bug, etc a complete waste of time.

If you ever get interested in knowing more about this bug, feel free to PM me.

Lance

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Apr 05, 2017 Apr 05, 2017

Copy link to clipboard

Copied

rlancemoody  wrote

Thanks Rikk,

To add insult to injury, it doesn't appear that this slow down issue has been acknowledged at all, making this 6 months old thread and the offers I and others have made to more fully help document the bug, etc a complete waste of time.

Lance

Lance,

If you provide me a link to the unacknowledged post on the feedback.photoshop.com site where you've provided information, I would be happy to take a look. I searched for your user name but didn't come up with anything.

The information we need you to provide is:

Hardware Specs for your machine
OS and Version number.
Lightroom version number (From Help>System Info...)A specific Lightroom operation description

An elapsed time in seconds.

Example:

"I am running a 2012 Macbook Pro with 16 GB of Ram an 250gb SSD that has 95 GB free. It is currently running OSx 10.12.3.
My Lightroom version is CC2015.9.
When I try to export 200 JPEGs from raw files to my local hard drive, it takes 25 minutes. Lightroom x.x only took 10 minutes."

Too often we get this:

"Lightroom is so slow I can't do anything,  Hot machine - latest updates and I just sit and watch it spin. When are you going to do something? "

Honestly, I would love to figure out what is causing your and other's slowness issues but I need good information to understand what is slow, how slow it is and how to duplicate it on one of my computers. The best thing you can do is find your(or another's)thread at the link I provided and add your information to the information already there. If no thread exists, create one. It is the surest way to have your issue tested, verified, and fixed.

Realize too that we are continuing to work on performance and just because one issue has been fixed doesn't mean we aren't looking for more ways to optimize the user's experience.

Rikk Flohr - Customer Advocacy: Adobe Photography Products

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Participant ,
Apr 05, 2017 Apr 05, 2017

Copy link to clipboard

Copied

Alright, I'll copy my post above which hopefully includes the info you need over to the other site.

Lance

Here's what I posted there:

There is simply no question that LR 2015.9 (and earlier) slows down with continued use during a session.

This is easy to replicate and demonstrate.

Lightroom starts up responsive and quick and, after a short while of working with images, begins to bog down: screen redraws, edits, crops etc all start to take longer and longer to accomplish.

Ultimately, previously instant tasks start taking 5 seconds or longer.

If you quit the app and restart the behavior resets to good response but then repeats as above.

Windows 10

Intel 6950X

256GB RAM

2/Nvidia Titan Pascals 2/Nvidia GeForce 1080's  (tried with and without acceleration on)

All SSD or M.2 storage less than half capacity

ALL LATEST VERSIONS OF DRIVERS/SOFTWARE

100GB Cache (purged before testing)

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Apr 21, 2017 Apr 21, 2017

Copy link to clipboard

Copied

In my case it has been unusable since I switch from Mac to W10.

I am on a Dell Xps 15 (9560), full specs (32GB ram, i7, nvidia 1050).

It is completely unusable.

I am a (pro) LR user since version 1.

Never had such a horrible experience with it.

I need your help, because it isimpossible to work this way. I am either switching back to mac, ot have to find alternatives.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Apr 26, 2017 Apr 26, 2017

Copy link to clipboard

Copied

I'm new to Lightroom, having just switched from Photoshop Elements 15. I am using a Dell XPS 13 2-in-1 with i7-7Y75 CPU, Intel 615 GPU, 16HB RAM, and 1TB SSD hard disk. The laptop's resolution is 3200x1800, but I use Lightroom on an external UHD (3840x2160) monitor via a Thunderbolt dock. Window 10 Home Edition.

I installed Lightroom less than a month ago and it identifies as 2015.10. Unfortunately I find the performance makes the program almost unusable. I imported 500, 24 megapixel raw images yesterday and it took over an hour. In PSE it would have taken less than 10 minutes. Going through the images afterwards is painful, taking 3+ seconds to open up a full screen preview on each image. In develop mode every operation also takes 3+ seconds. If I want to do any serious spot removal or other touch ups it's a lot quicker to bring the image into Photoshop, which seems to work fine on my hardware.

I've tried turning the GPU on/off, but can't see any difference regardless of the setting. I've increased the cache size to 50GB but it doesn't seem to help. I turned on Smart Previews for all images and that made some difference, but not enough to make it usable. Are there any other settings I should consider?

Since I am new to LR, I took a short CD-based course but it didn't cover performance settings. I've done lots of Google searches but so far haven't found anything that helps. I'm worried that my hardware might not be suitable for LR.

Any suggestions on a solution would be greatly appreciated.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Participant ,
Apr 27, 2017 Apr 27, 2017

Copy link to clipboard

Copied

Yeah, still the same terrible behavior in new version: fast performance degrades during session until LR becomes almost unusable.

I filed the report a while ago.  Offered to make a video demonstrating behavior, etc.  Have not heard anything from Adobe.

Nowhere to turn to with these guys. And no help on the horizon.

Lance

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Apr 27, 2017 Apr 27, 2017

Copy link to clipboard

Copied

I opened up a chat session with a support person and all he did was delete my prefs file (something which I had already done). I told him I would have to do more testing and get back to him. Today, things are just as slow as ever.

Is anybody from Adobe listening????

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Apr 27, 2017 Apr 27, 2017

Copy link to clipboard

Copied

There is some light on the horizon. In a post by Simon Chen, found in this page: Lightroom: Slow performance on Xeon CPUs | Photoshop Family Customer Community  (sorry, I don't know how to point to the exact post, but I've copied the text below.

In summary, I found that this temporary patch hasn't FIXED all the problems, but its made most of them a lot better, at least for me. I can now move between large image files faster, and unless I do many complex edits, I can go as many as 15 images without having to shut down and restart lightroom. Exports are also running faster on my machine.

Full text cut-and-paste of Simon Chen's post:

There has been some under-the-hood threading changes in Lr CC 2015.10 (Lr 6.10), the team like to hear your feedback on if anything has changed for you with the Lr CC 2015.10 (Lr 6.10) update.  Furthermore, we have added some configuration flag that allows tweaking how Lightroom makes uses of the multiple CPU cores. If the problem still persists, you could do a test as described below and report back if you can get improved interactive editing performance:

  1. Open Lightroom.
  2. Invoke Lightroom > Preferences... menu command
  3. When the Preferences dialog appears, select the Presets tab.
  4. Click on the button labeled “Show Lightroom Presets Folder...”
  5. Lightroom will reveal the root preset folder in the Finder/Explorer.
  6. Now goto https://adobe.ly/2oqzWOX and download the config.lua file and copy it into the Lightroom preset folder that Finder/Explorer selected at step 5. The config.lua file will set a ratio (<=1.0, default is 1.0) on the maximum number of concurrent threads that Lr would use as relative to the total number logical CPU cores on the machine.
  7. Relaunch Lr. If you did step 1 though step 6 correctly, you should see the following entry reported in Lightroom's System Info dialog, which will essentially instruct Lr to not use more than the number of physical CPU cores of threads plus 1.

Config.lua flags:

Develop.AdjustMaximumThreadCount = 0.51

     8. Now do your normal thing in Lr and report back your experience.You can further tweak the value of "AdjustMaximumThreadCount" in the config.lua file to see if things changes for you.

     9. Remove or rename the config.lua from the Lightroom preset folder after the experiment.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Participant ,
Apr 27, 2017 Apr 27, 2017

Copy link to clipboard

Copied

I am testing this now and will report back here and at the referenced thread above.

Edit:

Ah yes, no real improvement to report.

I confirmed that the LUA was in place in working.

There MIGHT be a small increase in the time until the app slows down so much that it is torture but I may be imagining that.

But again the app works fine when first started up--responsive and quick but after working with images I begin to notice a slowdown that increases over time.

For instance, flagging a reject, waiting for it to disappear and the new image to be displayed is very quick immediately after opening the app then the time for this to happen becomes longer and longer 1 second 2 seconds 5 seconds etc.

This is completely reproducible. And I have offered to help the Adobe team identify the issue.

Thanks,

Lance

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Participant ,
Apr 27, 2017 Apr 27, 2017

Copy link to clipboard

Copied

So many people on that other thread reporting the same thing.

It is amazing that Adobe cannot get a handle on this.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Apr 29, 2017 Apr 29, 2017

Copy link to clipboard

Copied

I tried this patch but didn't see any improvement. I imported a batch of 200 photos and it was painful going through them. It seems every mouse click has a 3+ second delay, even the most trivial operation.

Something is seriously wrong with this product.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Mar 31, 2017 Mar 31, 2017

Copy link to clipboard

Copied

Well it was a blissful couple week but the same problem has surfaced all over again tonight.  Seems ridiculous that I'm going to have to try and go through another whole clean install in the hopes of fixing it.  Ugh..

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines