Lightroom 2015.7: I recently upgraded now Exporting and Loading brushes takes a LONG time

  • 1
  • Problem
  • Updated 10 months ago
  • (Edited)
I upgraded to Lightroom 2015.7 and now Exporting and Loading brushes takes a LONG time.

I have an Asus G750JW it is kept upto date and is error/virus free. 

4 days ago I upgraded to 2015.7 and since have experienced extremely slow export speeds (which almost disables lightroom until complete) and loading of brushes takes forever.

I installed the previous version again in hopes that it fixes the issue, however, I get the same results.

I have optimized and done a disk clean up, which has not resolved the issue either. Thoughts? I see a lot of others reporting this issue as well.
Photo of Shannon Bileski

Shannon Bileski

  • 5 Posts
  • 0 Reply Likes

Posted 2 years ago

  • 1
Photo of Frank Chan

Frank Chan

  • 47 Posts
  • 5 Reply Likes
I had a similar problem.

I shot a wedding last weekend (10/01/2016) and tried to use LR 6.7 to do the edits. I had to fall back to LR 6.3 (needed to get my work done) because LR 6.7:
* took at least 2 minutes or more to become completely usable upon start-up (a lot of the startup time was in a “not responding” status).
* the Develop module was sluggish at best.
* took more than 5.5 Hrs to export 1244 JPG files using 3 simultaneous parallel processes (while LR 6.3 took about 2 Hrs for 1244) and more importantly, the JPGs from LR 6.7 didn’t look good at all (not sure if it was the lens chromatic aberration correction I used, no time to test).
System:
Windows 10, ver 1607, build 14393.187, 64 bit
Asus N550JK-DB74T, Intel i7-4710HQ, 16 GBs
500 GBs Samsung 850 EVO SSD
GPU Nvidia GTX 850M 2 GBs driver 368.81
BenQ 4K UHD monitor

Need LR 6.7 for my 5D Mark IV
Any help will be greatly appreciated.  Hope this gets resolved!
Photo of Shannon Bileski

Shannon Bileski

  • 5 Posts
  • 0 Reply Likes
So this is what I did to get it working fast again...

I uninstalled it from my PC, then reinstalled the CC 5 version and did the upgrade from there. I then renamed my preferences folder to Preferences_old and created a new Catalog. Now working great!
Photo of Frank Chan

Frank Chan

  • 47 Posts
  • 5 Reply Likes

Thanks Shannon.  I'll try your fix when I get some extra time.  Hopefully, it's the Preferences folder/files that causes our problems.

In the meantime, can someone from Adobe LR (e.g., the site monitor) please versify that data structure of the  "Lightroom 6 Startup Preferences.agprefs" file, the "Lightroom 6 Preferences.agprefs" file and/or the LR 6.3 Catalog has changed (or not changed) among all the updates from LR 6.3 to LR 6.7 that would possibly cause these performance problems (see my post above for the problems I experienced with 6.7).  More importantly, if the 6.7 catalog is different from the 6.3 catalog, is there a conversion procedure to execute?  In other words, am I out of luck with the content/work (many thousands of photos) in my 6.3 catalogs when using LR 6.7 with these older 6.3 catalog?  

Thanks

Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 4309 Posts
  • 1571 Reply Likes
> In other words, am I out of luck with the content/work (many thousands of photos) in my 6.3 catalogs when using LR 6.7 with these older 6.3 catalog?

No, any LR6 version can open any LR6 catalog, so you're fine.
Photo of Frank Chan

Frank Chan

  • 47 Posts
  • 5 Reply Likes
Thanks for your response.  And yes, this is what I would expect.  None-the-less, since I'm having a problem, every LR 6 component is under suspect until you find out otherwise.  Thanks again for taking the time to respond.
Photo of Shannon Bileski

Shannon Bileski

  • 5 Posts
  • 0 Reply Likes
System info as requested...
Lightroom version: CC 2015.7 [ 1090788 ]
License: Creative Cloud
Operating system: Windows 10
Version: 10.0
Application architecture: x64
System architecture: x64
Logical processor count: 8
Processor speed: 2.3 GHz
Built-in memory: 24493.4 MB
Real memory available to Lightroom: 24493.4 MB
Real memory used by Lightroom: 3349.7 MB (13.6%)
Virtual memory used by Lightroom: 3757.5 MB
Memory cache size: 1360.9 MB
Maximum thread count used by Camera Raw: 8
Camera Raw SIMD optimization: SSE2,AVX,AVX2
System DPI setting: 96 DPI
Desktop composition enabled: Yes
Displays: 1) 1920x1080
Input types: Multitouch: No, Integrated touch: No, Integrated pen: Yes, External touch: No, External pen: Yes, Keyboard: No

Graphics Processor Info:
GeForce GTX 770M/PCIe/SSE2

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


Application folder: C:\Program Files\Adobe\Adobe Lightroom
Library Path: F:\2016 Catalogs\2016_1\2016_1.lrcat
Settings Folder: C:\Users\Shannon\AppData\Roaming\Adobe\Lightroom

Installed Plugins:
1) AdobeStock
2) Canon Tether Plugin
3) Evlaa
4) Facebook
5) Flickr
6) HDR Efex Pro 2
7) Leica Tether Plugin
8) LRT Export 4
9) Nikon Tether Plugin

Config.lua flags: None

Adapter #1: Vendor : 10de
    Device : 11e0
    Subsystem : 213e1043
    Revision : a1
    Video Memory : 3039
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 770M/PCIe/SSE2
GL_SHADING_LANGUAGE_VERSION: 4.50 NVIDIA
GL_STENCIL_BITS: 8
GL_VENDOR: NVIDIA Corporation
GL_VERSION: 4.5.0 NVIDIA 369.09
GPUDeviceEnabled: false
OGLEnabled: true
GL_EXTENSIONS: GL_AMD_multi_draw_indirect GL_AMD_seamless_cubemap_per_texture 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_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_program_interface_query GL_ARB_provoking_vertex GL_ARB_query_buffer_object GL_ARB_robust_buffer_access_behavior GL_ARB_robustness 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_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_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_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_provoking_vertex GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_separate_shader_objects GL_EXT_separate_specular_color GL_EXT_shader_image_load_store GL_EXT_shader_integer_mix GL_EXT_shadow_funcs 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_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_square GL_NV_command_list GL_NV_compute_program5 GL_NV_conditional_render 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_float_buffer GL_NV_fog_distance GL_NV_fragment_program GL_NV_fragment_program_option GL_NV_fragment_program2 GL_NV_framebuffer_multisample_coverage GL_NV_geometry_shader4 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_pixel_data_range GL_NV_point_sprite GL_NV_primitive_restart GL_NV_register_combiners GL_NV_register_combiners2 GL_NV_shader_atomic_counters GL_NV_shader_atomic_float 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_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_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 Frank Chan

Frank Chan

  • 47 Posts
  • 5 Reply Likes

Later on this week I'll have some time to work on the performance problem with LR 6.7 I'm experiencing. 

 Like Shannon, instead of applying all the updates to my LR 6.3, I'm thinking of just uninstalling LR 6.3 then re-installing the download copy from the Adobe LR 6 site and applying my product key.

So I don't waist time, can someone tell me if the LR Application Installer at helpx.adobe.com/lightroom/kb/lightroom-downloads.html contain all the LR 6 updates up to and including LR 6.7? This will allow me to get an untainted fresh copy of LR6.7 which hopefully will perform as good as or better than LR 6.3.  And hopefully the LR 6.3 catalog is totally compatible with LR 6.7 too.

I need to get this working for my 5D Mark IV raw files.  And I don't want to use the DNG converter if at all possible or apply some risky "hack" to get these raw files working in LR 6.3. 

And by the way, I tried the standalone DNG converter and it does work for these raw files.

Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 3850 Posts
  • 729 Reply Likes
Follow the instructions here: http://blogs.adobe.com/lightroomjournal/2013/06/keeping-lightroom-up-to-date.html 

You should be installing 6.0 and then the 6.7 update. 
Photo of Frank Chan

Frank Chan

  • 47 Posts
  • 5 Reply Likes

Thanks Rikk for your response.  I think I will have some time to try this "refresh" by Friday.

BTW, I can't find any where on the keeping-lightroom-up-to-date site that explicitly says that any given update contains all the updated components of the previous updates.  So for a user, the only safe course of action is to assume that one needs to apply all the updates in sequence to become current and similarly for the LR 6 application installer (i.e., doesn't say explicitly a vanilla version with no updates applied).  Never-the-less, thanks again for this telling me this official LR information.  This will save me a lot time & effort. 

And keep your fingers crossed for me that this refresh works ;-)       

Photo of Frank Chan

Frank Chan

  • 47 Posts
  • 5 Reply Likes

I tried the LR 6 refresh & apply LR 6.7 update method, but I'm still experiencing very slow performance when starting, using some Develop tools and especially exporting large numbers of photos to JPGs.   So I went back to LR 6.3 and I'll try some other means to get my 5DM4 files imported (e.g., DNG Converter, ... .).  Maybe the LR 6.7+x update will perform better once it's released (and it should be soon to support the new Canon 24-105 f/4 L II Lens).  I'll just hang tight 'til then.  ;-(


Photo of Shannon Bileski

Shannon Bileski

  • 5 Posts
  • 0 Reply Likes
Things have slowed down again for me. Processed 2 shoots on the same catalog and was fine. Now working on the third - dramatic slow down again. Not sure what is happening. Total images in library 863.
Photo of Frank Chan

Frank Chan

  • 47 Posts
  • 5 Reply Likes

Sorry to hear you are having similar export performance problems again with LR 6.7.  I guess I’m not alone.

Just to let you know, I did a cursory test of LR 6.7 exporting 1200 photos after my LR 6 refresh & LR 6.7 update.  Using Task Manager, the Resource Monitor and monitoring the LR process bars (Note: Started 3 simultaneous exports at 400 photos each; This is my normal way of doing large batches.), it looks to me that things start slowing down after about 30% of the total photos have been written out.  Throughout the entire export, CPU runs about 35% to 50% and memory no more than 50% of 16 GBs is being used.  For I/O, no more than around 7% to 10% for the first 30% is being used, but after the 30% or so are done, I/O slows to about 1% to 2%.  I can see this slowness in Task Manager as well as how the OS is allocating and releasing files in the Resource Monitor (i.e., rate of allocation & release of files not as frequent.)  So given this, I suspect that the export process is “spinning/looping” CPU wise within itself once the 30% have been completed.

Do you see the same behavior when you tried your 6.7 exports?

Photo of Shannon Bileski

Shannon Bileski

  • 5 Posts
  • 0 Reply Likes
Not sure, I am only processing one file at a time. I process...I export! lol
Maybe I should start exporting in batches to save time on the processing time and just walk away!
As mentioned above. Once the catalog had the 3rd shoot in it and started to process it slowed down dramatically. Now takes approx. 1.5 mins to export 1 file. :/
Photo of Frank Chan

Frank Chan

  • 47 Posts
  • 5 Reply Likes
Thanks for your quick reply.  Meanwhile, I'll keep my fingers crossed that LR 6.7+x will work for us much better.  Until then, I guess I'll have to just live with LR 6.3 ;-(.
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 3833 Posts
  • 724 Reply Likes
Shannon, did closing and reopening Lightroom help the speed?
Did restarting your computer help speed?
Photo of Frank Chan

Frank Chan

  • 47 Posts
  • 5 Reply Likes
Shannon, have you tried the new LR 6.8?  And if so, did you notice any improvements in batch export performance?  As for me, I haven't tried it yet and hope to try it some time next week.
Photo of Frank Chan

Frank Chan

  • 47 Posts
  • 5 Reply Likes
Shannon,  Just to let you know.  I installed 6.8 and am editing my 12/10 wedding.  So far 6.8 is much better than 6.3 & 6.7.  It starts fully in about 40 seconds now (i.e., no more “not responding” messages and waiting 2 minutes).  Tools are much more responsive, even better than even 6.3.  I hope to try exporting about 700 photos maybe tomorrow once I finish editing all of them.  I have about 400 more to edit.  My hope is exporting will be just as fast or better than 6.3. 
Photo of Frank Chan

Frank Chan

  • 47 Posts
  • 5 Reply Likes
Finished editing 771 photos and ran the 6.8 export. Unfortunately, the performance of the 6.8 export has not improved at all.  It took 3Hrs.&5Min. to complete.  Never-the-less, the Develop module has improved a lot compared to 6.3 and especially improved greatly compared to 6.7.  6.8 starts much faster and tools are much more responsive.  So given the performance of the Develop module, I'll stick with 6.8 for now and hope that the export process in the next release will be faster.
Photo of Brandon Gross

Brandon Gross

  • 2 Posts
  • 0 Reply Likes
Hi, I've been having the same problems Frank and Shannon have described. I'm currently using 6.8 and exporting is still extremely slow. I've tried multiple concurrent exports and just a single large export. Both still take between 6-8 hours to export around 2000 photos.

I've tried everything I can think of to increase performance and I'm currently waiting on a call back from level 2 support to address the issue further.  
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 3833 Posts
  • 724 Reply Likes
Brandon,
I am researching Export times since we've seen a few comments since the CC2015.8 update. I just ran 2000 PSD files export to JPEG and it took a little over 24 minutes. I ran 2000 Tiff files to JPEG and it took a little over 40 minutes. 

In order to understand why some of you are seeing extraordinary export times I would like to get some information.

2000 Images: File Format of original and approximate size each. 
2000 Exported JPEGs: Final pixel dimensions of each? 
Location of originals (local, external, network) and the path: 
Free space on drive containing originals:
Location of final export ((local, external, network) and the path):

Computer Manufacturer:
Operating System/Version:
Ram:
List of all attached peripherals:

If you would be willing to share your JPEG export settings that would be great too:

I am going to post this on the forum as well to ensure you see it. 


Let's see if we can get to the bottom of this!
(Edited)
Photo of Frank Chan

Frank Chan

  • 47 Posts
  • 5 Reply Likes

Thanks Rikk for your help.  I'll hope to gather this info for you when I get some time tomorrow morning.  Hope we can find the cause and have a fix/work-around for us soon.

Frank

Photo of Brandon Gross

Brandon Gross

  • 2 Posts
  • 0 Reply Likes
Hey Rikk,

Thank you so much for getting back with me. I've answered your questions below:

1. File Format and Original Size: Canon RAW .CR2 and roughly 28MB each

2. Final Dimension:  Roughly 5040 x 3380 Jpg

3. Location of Original RAW files:  They reside on a Pegasus2 R6 RAID 5 set through thunderbolt. It is locally attached to a Mid 2011 mac mini running Sierra 10.12.2 and LR version 2015.8. The path to the local RAW files is /Promise Drive II/Photos/2017/"name of the RAW files folder"

4. Free space on Drive with Originals: 5.69 TB

5. Location of exported Jpg's: They export to the same Pegasus2 R6 Drive to the path: /Promise Drive II/DELIVERABLES/Downloaded photos/FINISHED SETS/"name of export folder"

I should also mention the LR catalog files reside on the Server HD which is a Samsung EVO Pro SSD 512GB. 

I have also set a 200GB cache folder on a separate Promise Pegasus R4 Drive. It has around 1.25 TB of free space and is also set to RAID 5.

6. Computer manufacturer: Apple Mac Mini (mid-2011) Core i7 2GHz, 8GB Ram, Thunderbolt 1, Intel HD Graphics 3000 512 MB, Sierra 10.12.2.

7. Attached Peripherals: Caldigit Thunderbolt Station, Pegasus R2, Pegasus2 R6, Lacie 2Big thunderbolt, Another Lacie 2Big Thunderbolt, G-drive 1TB Firewire 800 drive (this only contains old legacy photos, so it's not accessed much), Samsung S24D300 Monitor, Dell SE198WFP Monitor. Brother MFC-L2700DW Multifunction Printer, Epson Artisan 1430 Printer. 

Network Traffic is Cat5e run through a Netgear ProSAFE GS116NA 16-port switch. My internet access is routed through an Airport Extreme (newest version).

8. JPEG Export Settings:  I export to the path I mentioned above, put into a subfolder, and I use file renaming (a custom profile I created.) It renames the file using a specified custom-text>a sequential number>the original file number. It would look like this: brandon_test_00001-05882.jpg. 

I should also mention, I have been using the JPEGmini Pro Lightroom plugin. I just did a test by removing this plugin from the export and it did increase the speed somewhat but I'm still looking at around 4 to 4.5 hours for 2000 photos based on my test. 

If you need any additional information, just let me know. I really appreciate you digging into this deeper. 

Thanks,

Brandon
Photo of Frank Chan

Frank Chan

  • 47 Posts
  • 5 Reply Likes

Rikk, Here's my list.  Hope a solution can be found 

* File Format of original and approximate size each?
     JPG 6720x4480 From 7MBs to 11MBs, averageing about 9.5MBs 

* Exported JPEGs Final pixel dimensions of each?
    JPG 6720x4480  From 9MBs to 15MBs, averageing about 12.5MBs 


* Location of originals (local, external, network) and the path?
     Local SSD, D:\_2016Photos\2016-12-10_Client\2016-12-10_ClientOrgs\2016-12-10_HH-MM-SS-nn-F.JPG

* Free space on drive containing originals?
    Local SSD 200GBs free

* Location of final export ((local, external, network) and the path)?
    Local SSD D:\_2016Photos\2016-12-10_Client\2016-12-10_ClientFinal\_2016-12-10_HH-MM-SS-nn-F.JPG


* Export Settings:

Rename output file:
    Add an _  (underscore) to the beginning of original file name as output file name (e.g., _2016-12-10_HH-MM-SS-nn-F.JPG)

   File Setting:
     JPEG, Quality 100%,  sRGB

  Image sizing:
    Resize not checked
    Resolution 300ppi

  Output Sharpening:
    not checked

  Metadata:
    All Metadata, remove Person Info, Remove Location Info, Write Keywords- not checked

  Watermarking:
    not checked

* Post-Processing:
    none


System:
  Windows 10 Home, ver 1607, build 14393.479, 64 bit
  Asus N550JK-DB74T, Intel i7-4710HQ 2.50GHz, 16 GBs RAM
  500 GBs Samsung 850 EVO SSD
  GPU Nvidia GTX 850M 2 GBs driver 376.19
  BenQ 4K UHD monitor using DisplayPort connection


Additional Notes:
  * Was going to use LR 6.3 to do edits & export so shot JPGs with 5DM4, LR 6.7 too slow.
  * Installed new LR 6.8 and it worked ok for editing, very slow exporting
  * LR Catalog only contains the 771 photos being edited & exported (i.e., one catalog/client).
  * LR Catalog is in the same high level folder path as originals & output photos folders.
  * Always do an integrity-check/back-up/optimize catalog/shutdown LR process.  Then restart LR and immediately start 3 simultaneous batch exports processes, in this case 257 photos each process, directing the output to 3 different file folders for each process. 

My hope is that LR 6.8 exports would run at least as fast as LR6.3
Frank

Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 3833 Posts
  • 724 Reply Likes
Brandon, 

Attempting to duplicate your example (I already did Frank's on Windows below)

To establish a baseline with my most similar system: Running MacBook Pro Retina (2012), 16 GB of Ram with Sierra installed (up to date as of yesterday) Lightroom CC2015.8.   Created a 2000 image catalog of Canon 5d Mark II raw files. Copied to MacBook.  Free space 112 GB on a 250 GB SSD. 

Restart Mac
Idle 5 minutes
Launch Lightroom with test 2000 image catalog
Idle 10 minutes
Export to 2000 full-size JPEG using your settings to local drive. 
Elapsed Stopwatch time: 1:30:44
No Export Plugins in use

Not as zippy in a file per minute basis as my Windows test but still quite a bit faster than what you are currently seeing.  Of course, I am not duplicating your test with example with 100% accuracy - just getting as close as I can. 

Keep in mind, fresh boot and no other programs running so I can have consistent testing. I am not sure how much load your computer was under in your tests. 

Update: I did perform the identical test with an uninstall of CC2015.8 and reinstall of 6.7 and the difference in time was about 14%. It did not vary as wildly as the times reported here. 

In any case, I could not get a 2000 image export to take longer than about an hour and half. 

Other usual suspects to consider: additional programs running in the background, virus software, hardware bandwidth limitations.
(Edited)
Photo of Frank Chan

Frank Chan

  • 47 Posts
  • 5 Reply Likes

Hi Rikk,

Just to let you know, I reverted back to 6.3.  I couldn't live with the 6.8 export slowness and the productivity I will lose that I can foresee in my up-coming work.

To help me make this decision, I compared 6.8's export time to 6.3's export time and found that 6.3 is a little more than twice as fast as 6.8.  Moreover, I guess I can live without the 5DM4 raw processing in 6.8 & 6.7. The 5DM4 .JPGs are really good and after editing & exporting them, the resulting .JPGs are just fine and the tools in 6.3 work good enough for what I normally use.  Never-the-less, I'm glad to see that the responsiveness of the 6.8 Develop tools were improved (at least they are now usable compared to 6.7).   My hope is that the export performance will be fixed in the next release (6.9 I guess) to at least match the export performance of 6.3. 

By the way, here's how I did the compare.  I edited my 12/17 540 event photos with 6.8 then ran the export.  The 6.8 export took 206 minutes.  Then I reverted back to 6.3 then ran the export with the same 540 photos that were edited with 6.8 (i.e., same catalog).  The 6.3 export took 98 minutes.

If you would pass this info back to the team that makes improvements, that would be great. 

Thanks,
Frank

(Edited)
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 3850 Posts
  • 729 Reply Likes
Thanks to all of you who chimed in with system stats, export settings and the other information. I have constructed a series of tests based upon these posts and will be reporting to the engineering staff. 
Photo of Frank Chan

Frank Chan

  • 47 Posts
  • 5 Reply Likes

Thanks so much Rikk for your effort and for taking our posts seriously.  In addition, if there is any more info you may need from me, I would be more than happy to provide any details your team may need to get this issue resolved.  To that end, I would love to see the export performance of LR 6's next release go faster.  This way I can keep my LR 6 up-to-date and especially to be able to use 5DM4 raw files with LR 6.

Happy Holidays!
Frank    

Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 3850 Posts
  • 729 Reply Likes
Frank, 

We still have an unexplained difference. I created a 650 image collection of images (a mix of JPEGs, DNGs (including Panos and HDRs), Tiffs and PSDs and exported them using the JPEG settings you listed above. In CC2015.7 the export took 12 Minutes and 1 Second and in CC2015.8, it took 12 Minutes and 4 seconds (probably within my stop watch finger margin of error...) 

To keep my tests rigid for comparison, I installed the LR version(.7). Rebooted. Waited 5 minutes. Launched Lightroom and loaded the collection. Waited 10 minutes. Exported.  Then I uninstalled LR version and installed the next version and repeated.The wait times are to ensure that no background loading or other application installation/update is fouling things.  

I am still continuing to test but my export is running at about 8X your speed on your faster export.  

I will be running a similar test over the weekend on Mac OS to see if it is comparable. I will keep you posted. 
Photo of Frank Chan

Frank Chan

  • 47 Posts
  • 5 Reply Likes

Hi Rikk,

I have the LR 6.0 DVD version installed then installed the LR 6.x releases.  Does having the non-Creative Cloud version make any difference especially since there are features "turned off" in the DVD version?  So can you run your tests using a DVD version to make sure that don't make any difference for you.

And is there a way to turn on an internal LR trace log for just a few minutes while the export is running?  This way I can send you the log so the team can see what's going on.  And as a last resort, I can try to set up and turn on a Win10 OS level trace log while the export is running.  As I can remember, I can do this using Win10's Resource Monitor.  Or if someone there can give me a Resource Monitor script to load that would be even better.  Hopefully with a log, we can see what's going on in detail.

Thanks again for your help & effort.  And more importantly, have Merry Christmas!
Frank

      

Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 3850 Posts
  • 729 Reply Likes
The versions are identical. The only difference happens when you enter a license vs sign in with a Creative Cloud ID.  For example, here, I installed the 6.7 version but updated it to CC2015.8 for the second part of the test.  

The team is out on Winter Holiday Shut-down till January 3rd but they are watching this thread. 
Photo of Frank Chan

Frank Chan

  • 47 Posts
  • 5 Reply Likes

Hi Rikk,

To get a better ideal of why LR 6.8’s export take more time to complete vs LR 6.3’s export using my PC, I set up 2 identical Windows 10 Performance Monitor data collector sets, one for LR 6.3 and one for LR6.8.  This way we see what each version is doing CPU & IO wise from Win10’s point of view.

To collect the data, I exported the same set of 540 JPGs using the same export settings from the same LR 6 catalog using LR 6.3 & LR 6.8 (at different times of course).  And while the exports were running, I started the data collectors with a 5-minute duration at about 1 minute after the export started, 40%, 60%, 90% and 96% export completion intervals.  By the way, the exports took 137 minutes for LR 6.8 and 104 minutes for LR 6.3.

Looking at what stands out in the report for each data collector run, the amount of threads spawned by LR 6.8 are thousands more than LR 6.3 which may cause the total CPU time for LR 6.8 to be reduce compare to LR 6.3.  As a representative example of what all the reports are showing, below are the reports for LR 6.3 & LR 6.8 taken at the 60% export completion interval.  I also added color eye catchers for easier reading.

Hope this helps,
Frank.

Photo of Frank Chan

Frank Chan

  • 47 Posts
  • 5 Reply Likes

Hi Rikk,

Any response from the team to my findings about LR 6.8 spawning 10 times more threads vs. LR 6.3 causing export performance slowness of .JPGs?

Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 3833 Posts
  • 724 Reply Likes
Export performance is being reviewed for the next update. 
Photo of Frank Chan

Frank Chan

  • 47 Posts
  • 5 Reply Likes

Thanks so much Rikk for your reply and to the team for taking this export performance issue seriously.  And by the way, I made a mistake in my last comment above.  It's not 10 times more threads spawned by LR 6.8 vs. LR 6.3 but It's 100 times more threads.

Thanks again,
Frank  

Photo of Frank Chan

Frank Chan

  • 47 Posts
  • 5 Reply Likes

Hi Rikk,

I see LR 6.9 is out and that the release notes say that export performance degradation issues where fixed. I'll try it out when I get a chance.  Thanks

Photo of Frank Chan

Frank Chan

  • 47 Posts
  • 5 Reply Likes

I tried a quick export test of 677 JPGs.  Lr 6.9 took 2Hrs. 28Min. vs Lr 6.3 1Hr. 40Min

Noticed Lr 6.9 thread count ranging from 75 to 150 most the time with spikes to 200 on occasion.  I guess good news vs. Lr 6.8 in the ten thousand range.

Haven't tried the Develop module responsiveness yet.

Photo of Frank Chan

Frank Chan

  • 47 Posts
  • 5 Reply Likes

Hi Rikk,

Just to get back to you, the good news is that LR 6.9’s Develop module  responsiveness is good, similar to LR 6.8 and much better than LR 6.3.  And 6.9’s Export has improved a little over 6.8’s but still not as fast as 6.3’s.  To compare, here’s my export rates.

Export Rates:
LR 6.9, 4.57 JPGs/min.
LR 6.8, 4.17 JPGs/min.
LR 6.3, 6.77 JPGs/min.

All-in-all, I guess I’ll stick with 6.9 and hope LR’s Export speed will continue to improve in future releases.  More importantly, please thank the LR team for their effort to improve LR's Export speed.

Frank Chan

Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 3833 Posts
  • 724 Reply Likes
The team continues to hammer on all performance issues. Hopefully you will see more improvement in the future!
Photo of Frank Chan

Frank Chan

  • 47 Posts
  • 5 Reply Likes
Guess what!  I got LR CC Classic to run exports a little more than 3 times faster than before (e.g., 887 photos took 50 Min. vs 3Hrs.), as well as the develop module runs so much faster and smoother too, no sluggishness at all.   The fix was to buy a new PC.

Here's the spec on my new PC.
Lightroom Classic version: 7.0.1 [ 1142117 ]
License: Creative Cloud
Operating system: Windows 10
Version: 10.0 Windows Home 1703, Build 15063.726
Application architecture: x64
System architecture: x64
PC Brand: ACER Predator G3-710
Processor: Intel i7-7700 CPU @ 3.60GHz
Processor cores: 4
Logical processor count: 8
Processor speed: 3.6 GHz
Built-in memory: 32GBs
C drive (OS & APPs) Intel 256GB SSD
D drive (Photos & LR Catalogs) Samsung 850 EVO 500GB SSD
Real memory available to Lightroom: 32GBs
Real memory used by Lightroom: 1419.9 MB (4.3%)
Virtual memory used by Lightroom: 2044.6 MB
GDI objects count: 620
USER objects count: 1907
Process handles count: 1314
Memory cache size: 29.3MB
Maximum thread count used by Camera Raw: 5
Camera Raw SIMD optimization: SSE2,AVX,AVX2
Camera Raw virtual memory: 927MB / 16355MB (5%)
Camera Raw real memory: 965MB / 32710MB (2%)
System DPI setting: 142 DPI (high DPI mode)
Desktop composition enabled: Yes
Displays: 1) 3840x2160 Benq 4K UHD
Input types: Multitouch: No, Integrated touch: No, Integrated pen: No, External touch: No, External pen: No, Keyboard: No
Graphics Processor Info:
DirectX: NVIDIA GeForce GTX 1070 with 8GBs

So I believe that my old PC's Intel i7-4710HQ CPU with 16GBs of memory was the main reason for my slow export issues and the combination of the Intel i7-4710HQ CPU & Nvidia GTX 850M GPU with 2 GBs of memory caused the sluggishness of the develop module.  I know not everyone can afford to go out and buy a new bigger/faster PC just for LR.  But for me, I so glad I did; much happier now.

Frank Chan