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

PC Lightroom Classic 13.5 CPU and GPU low utilization issue

Community Beginner ,
Aug 27, 2024 Aug 27, 2024

Copy link to clipboard

Copied

Howdy! 

 

I have a fairly high powered machine. AMD 3950x (16core, 3.5GHz), 64GB Ram, Nvidia 2080 super (8gb vram), and dripping in Samsung 990 Pro M.2's. (Admittedly it was more of a beast in 2020 when I built it. 😉 It screams when I edit in in Premiere, simply tears through ProRes 4k video, both CPU and GPU ramp up to 90-100% utilization and run for hours. 

 

The problem occurs when I use Lightroom Classic...

I have an archive of 250k images on a Synology NAS (my archive for old projects) and active projects live on a 2TB Samsung 990 Pro M.2 (connected to the motherboard X570 Master) while I'm editing them. When I import/render previews (say 4k images from a shoot), it crawls...But not because the CPU and GPU are maxed out, as they run at 6-10% CPU and 1-4% GPU. Lightroom just doesn't seem to be trying. It's like it doesn't fully utilize my CPU and GPU. The only time I can get LR to utilize 100% CPU is when I'm scrolling through the grid and images that don't have previews come into view, then it will start working hard even going up to 100% CPU. But if I were to select all of those images and force it to render previews, LR would take 5 minutes to queue the task, then take 9 hours or so to render 700 images on Standard Preview.

 

Things I've tried...

  • Updated all drivers.
  • Clean install of windows 11. (and updated all OS things)
  • Fully uninstalled LR (event deleted presets)
  • Created a fresh LrCat from scratch (takes about three days to do)
  • Reformatted all drives with larger block sizes.
  • Moved the LrCat files to different M.2 Drives. 
    • Usually my LrCat files live on an M.2 drive that is backed up by dropbox. I have moved it to drives that aren't backup up, and it didn't change my issue. 

 

One of the big clues that this might be an issue was the purchase of a 2021 Macbook Pro M1 max. I started editing on the road more. I noticed that the Macbook would utilize 90-100% CPU when using LR. Imports, renders, exports, you name it... If it needed to work, it worked hard. Granted, I was using small catalogues for each shoot (4-12k images). 

 

Any help would be much appreciated. 

 

System Info: 

Lightroom Classic version: 13.5 [ 202408062022-6258095b ]
License: Creative Cloud
Language setting: en
Operating system: Windows 11 - Home Premium Edition
Version: 11.0.22631
Application architecture: x64
System architecture: x64
Logical processor count: 32
Processor speed: 3.5GHz
SqLite Version: 3.36.0
CPU Utilisation: 6.0%
Power Source: Plugged In
Built-in memory: 65451.5 MB
Dedicated GPU memory used by Lightroom: 269.7MB / 7987.0MB (3%)
Real memory available to Lightroom: 65451.5 MB
Real memory used by Lightroom: 2721.2 MB (4.1%)
Virtual memory used by Lightroom: 3108.1 MB
GDI objects count: 835
USER objects count: 2227
Process handles count: 5844
Memory cache size: 2110.5MB
Internal Camera Raw version: 16.5 [ 1953 ]
Maximum thread count used by Camera Raw: 5
Camera Raw SIMD optimization: SSE2,AVX,AVX2
Camera Raw virtual memory: 464MB / 32725MB (1%)
Camera Raw real memory: 468MB / 65451MB (0%)
 
Cache1: 
NT- RAM:0.0MB, VRAM:0.0MB, Combined:0.0MB
 
Cache2: 
m:2110.5MB, n:0.0MB
 
U-main: 162.0MB
 
System DPI setting: 144 DPI (high DPI mode)
Desktop composition enabled: Yes
Standard Preview Size: 3840 pixels
Displays: 1) 3840x2160
Input types: Multitouch: No, Integrated touch: No, Integrated pen: No, External touch: No, External pen: No, Keyboard: No
 
Graphics Processor Info: 
DirectX: NVIDIA GeForce RTX 2080 SUPER (32.0.15.6081)
Init State: GPU for Export supported by default
User Preference: GPU for Export enabled
Enable HDR in Library: ON
 
Application folder: C:\Program Files\Adobe\Adobe Lightroom Classic
Library Path: G:\Dropbox\SAFE\Lightroom Files\Catalogue Files Segmented Years\KWP LCat 2020-2030\Emergency Catalog\KWP LCat 2020-2030.lrcat
Settings Folder: C:\Users\kawal\AppData\Roaming\Adobe\Lightroom
 
Installed Plugins: 
1) AdobeStock
2) Flickr
3) Nikon Tether Plugin
 
Config.lua flags: 
 
Adapter #1: Vendor : 10de
Device : 1e81
Subsystem : 13a010de
Revision : a1
Video Memory : 7987
Adapter #2: Vendor : 1414
Device : 8c
Subsystem : 0
Revision : 0
Video Memory : 0
AudioDeviceIOBlockSize: 1024
AudioDeviceName: $$$/dvaaudiodevice/SystemDefaultAndEffectiveDeviceName=System Default - BenQ SW321C (NVIDIA High Definition Audio)#{comment}DVAAU-4201250: Open the audio hardware preferences page.
AudioDeviceNumberOfChannels: 2
AudioDeviceSampleRate: 48000
Build: LR5x120
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: 16384
GL_MAX_TEXTURE_SIZE: 32768
GL_MAX_TEXTURE_UNITS: 4
GL_MAX_VIEWPORT_DIMS: 32768,32768
GL_RED_BITS: 8
GL_RENDERER: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2
GL_SHADING_LANGUAGE_VERSION: 4.60 NVIDIA
GL_STENCIL_BITS: 8
GL_VENDOR: NVIDIA Corporation
GL_VERSION: 4.6.0 NVIDIA 560.81
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_polygon_offset_clamp 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_spirv_extensions 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_anisotropic 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_multiview_texture_multisample GL_EXT_multiview_timer_query 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_shadow_lod GL_EXT_texture_shared_exponent GL_EXT_texture_sRGB GL_EXT_texture_sRGB_R8 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_EXT_memory_object GL_EXT_memory_object_win32 GL_NV_memory_object_sparse GL_EXT_win32_keyed_mutex GL_KHR_parallel_shader_compile GL_KHR_no_error GL_KHR_robust_buffer_access_behavior GL_KHR_robustness GL_EXT_semaphore GL_EXT_semaphore_win32 GL_NV_timeline_semaphore GL_KHR_shader_subgroup 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_NVX_blend_equation_advanced_multi_draw_buffers GL_NV_blend_minmax_factor GL_NV_blend_square GL_NV_clip_space_w_scaling GL_NV_command_list GL_NV_compute_program5 GL_NV_compute_shader_derivatives GL_NV_conditional_render GL_NV_conservative_raster GL_NV_conservative_raster_dilate GL_NV_conservative_raster_pre_snap GL_NV_conservative_raster_pre_snap_triangles GL_NV_conservative_raster_underestimation 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_feature_query 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_barycentric 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_program_multiview GL_NV_gpu_shader5 GL_NV_half_float GL_NV_light_max_exponent GL_NV_memory_attachment GL_NV_mesh_shader 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_query_resource GL_NV_query_resource_tag GL_NV_register_combiners GL_NV_register_combiners2 GL_NV_representative_fragment_test GL_NV_sample_locations GL_NV_sample_mask_override_coverage GL_NV_scissor_exclusive GL_NV_shader_atomic_counters GL_NV_shader_atomic_float GL_NV_shader_atomic_float64 GL_NV_shader_atomic_fp16_vector GL_NV_shader_atomic_int64 GL_NV_shader_buffer_load GL_NV_shader_storage_buffer_object GL_NV_shader_subgroup_partitioned GL_NV_shader_texture_footprint GL_NV_shading_rate_image GL_NV_stereo_view_rendering 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_rectangle_compressed 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_uniform_buffer_std430_layout 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_linked_gpu_multicast GL_NV_gpu_multicast GL_NVX_gpu_multicast2 GL_NVX_progress_fence 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_OVR_multiview GL_OVR_multiview2 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 
TOPICS
Windows

Views

182

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
LEGEND ,
Aug 27, 2024 Aug 27, 2024

Copy link to clipboard

Copied

I don't know the reason why your CPU isn't being used more heavily on Import. However, Lightroom Classic does not use the GPU at import, and so what you are seeing for the GPU is expected.

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 ,
Aug 27, 2024 Aug 27, 2024

Copy link to clipboard

Copied

Good point. I was more thinking of import imediately followed by preview rendering. Not that it would be maxing out the GPU, but just engaging it more.

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
LEGEND ,
Aug 27, 2024 Aug 27, 2024

Copy link to clipboard

Copied

 

Library Path: G:\Dropbox\SAFE\Lightroom Files\Catalogue Files Segmented Years\KWP LCat 2020-

 

Adobe does not support LrC catalogs on a network share, be that a local server, a NAS, or the Cloud. The Cloud includes DropBox.

 

Some make this work. Some have better luck with DropBix than other Cloud services. But eventually ir fails, especially performance.

 

IF that Library path actually just indicates that the catalog is being synced to DropBox, then stop that, each and every edit will cause communication to DropBox, slowing down performance. Remover that LrC is a parametric editor, and as such each and every edit gets compounded on what proceeded, 

 

P.S. Adobe does apparently support photos on a Server Share, a NAS, or the Cloud. But many find they have issues later.

 

 

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 ,
Aug 27, 2024 Aug 27, 2024

Copy link to clipboard

Copied

Great points. That was weighing on me as a culprit for a few months. Then, I decided to switch the LrCat files to a non-synced drive...the low cpu utilization persisted. Also, I'd think that theory would also mean more CPU usage. E.g. Processor running at 100% and LR is running slow. Whereas my issue is LR running slow and CPU not spooling up. 

 

As for LR not cooperating with a NAS... I keep my LrCat on an internal M.2 Drive, whilst storing old projects on the NAS. Active projects are on another M.2 internal drive. Both have similar low CPU utilization. I've not ruled this out as an issue though. I just don't think I can go back to less redundant external hard drives. But if that solved the issue...maybe I would. The problem is that I have about +15TB of photos, so testing that theory is not cheap or quick.

 

Great input. Thank you for your time. I appreciate it. 

-K

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 ,
Aug 31, 2024 Aug 31, 2024

Copy link to clipboard

Copied

LATEST

Howdy! I added an update to this post. I'd love some feedback, when you have time. I believe it's all about syncing collections with Adobe cloud.

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 Expert ,
Aug 27, 2024 Aug 27, 2024

Copy link to clipboard

Copied

One thing to check: Is Generate Previews in Parallel enabled? It’s in Preferences at the bottom of the Performance tab. I’ve always assumed that if that option was disabled, Lightroom Classic would limit how many cores it uses for preview generation.

 

For example, your CPU has 16 cores. If Lightroom Classic is processing previews serially instead of in parallel, meaning it’s restricting itself to one or maybe two cores, then 100% divided by 16 cores and multplying by 1 or 2 would be…around 6-12% similar to what you said.

 

If you find that Generate Previews in Parallel is actually enabled on your system, then I guess you can throw out this theory and look at something else…

 

If you find that Generate Previews in Parallel is disabled on the Windows PC and enabled on the Mac, that could explain the difference.

 

Overall, this is what I would expect in Lightroom Classic:

  • Higher percentage of CPU core use should be seen during overall use, preview generation (on import or in background), face detection…
  • Higher percentage of GPU use should be seen during Develop editing, masking, AI features, AI Denoise, and export, because these areas are specifically known to support GPU acceleration. 
  • Sometimes usage of both CPU and GPU will be high, but because of what I describe below, I am not surprised if using of one is high and the other is low during specific high loads. 

 

For both video editing and still image photography, the more a feature is GPU-accelerated, the less I expect the CPU to be needed, so for example during exporting in Premiere Pro or Lightroom Classic, I’m not surprised at all if GPU use hits the ceiling while CPU use drops.

 

This also applies to hardware accelerators. For video rendering, if the codec being used is supported by a codec-specific hardware-based accelerator in the CPU/GPU, the CPU cores can end up with not much to do because they won’t be able to process the data as fast as the hardware-based accelerator. This is also very true for the computationally expensive AI Denoise on the Mac, which can now also be accelerated by the Apple Neural Engine. With AI Denoise being processed by the GPU primarily and the ANE helping out, there is really not much left that the CPU can constructively help with, so the CPU is typically largely idle during AI Denoise.

 

The Apple Neural Engine is an AI coprocessor/accelerator in hardware. This used to be a weird edge case, but not any more: With the rise of AI features, the new Microsoft Copilot+ PC hardware standard specifies that a Copilot+ PC must have a Neural Processing Unit or NPU and it needs to meet a specific performance threshold.

 

So where we used to think CPU/GPU, and now we think CPU/GPU/other accelerators, soon we will think of hardware usage percentages in terms of the mix of CPU, GPU, NPU, and other accelerators. And the more a specific workload is more efficiently processed by the other processing units, the more likely that all CPU cores will not be used for that particular workload.

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 ,
Aug 27, 2024 Aug 27, 2024

Copy link to clipboard

Copied

Great suggestion. I checked that too. It's has been running parallel. I checked that a while back and even wondered if I should turn that off. But your explanation makes sense as to why leaving that on would be better. 

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 ,
Aug 27, 2024 Aug 27, 2024

Copy link to clipboard

Copied

UPDATE: 

I decided to throw more time into a wild idea. I decided to start a new catalogue on my Macbook Pro 2021 M1 Max, 64GB. I thought it would take days to rebuild a new catalogue with the 250k images (like it does on my PC)...But... my Macbook looks to be making quick work of the task. I'd estimate it will take no more than 9 hours.  I'll report back tomorrow on whether it will perform as quickly once it's finished with the LrCat build. 

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 ,
Aug 31, 2024 Aug 31, 2024

Copy link to clipboard

Copied

UPDATE:

So I rebuilt the catalogue on my macbook pro and everything was running great. CPU and GPU utilization was great, nearly maxed during any task. I was nearly sold on the Mac being better at handling the LrCat. THEN things turned. I love having photos synced to the cloud. I love being able to access photos across my devices. BUT... This seems to be the culprit. As soon as I switched the cloud sync to the new Macbook Catalogue, CPU and GPU utilization dropped on the Macbook. Suddenly all the tasks took forever. Renders, reading metadata, converting to DNG, you name it...It now barely crawled. 

 

To make certain of this, I jumped back onto my PC onto the old Catalogue (now disconnected from cloud sync). AND it now utilizes 100% of the CPU! Clearly something with the cloud sync is kneecapping LR's ability to utilize the CPU. 

 

Why oh why can't I have LR sync to cloud?

 

PS. I have erased my entire cloud storage a couple of times during this process, as I've heard gremlins can occur when switching synced catalogues. Erasing my cloud storage did not affect the issue I'm having. 

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