Lightroom 6 / CC2015: Very slow UI response with background export(s) running

  • 45
  • Problem
  • Updated 1 year ago
Lightroom 6 / CC2015s UI reaction is very slow / sluggish when a background export is running. When three exports are running, the development module becomes virtually unusable.

In Lightroom 4 or 5 it was no problem at all to start up to three or four background exports - of course the UI, especially the development module, was considerably slower than normal, but definitely completely usable.

LR Version: CC 2015.0.1 (with 6.0.1 update), on Window 7 64. Processor is an i7-2600, there is 16 GB RAM. RAM does not seem to be exhausted, LR6 uses about 3...4 GB with 3 parallel exports.

Edit: It makes no difference whether GPU usage is turned on or off.
Photo of LRuserXY

LRuserXY

  • 426 Posts
  • 41 Reply Likes

Posted 4 years ago

  • 45
Photo of Ed

Ed

  • 3 Posts
  • 1 Reply Like
I did find that creating a new database (based on my old one) eliminated a lot of speed issues. Exports still seem to suffer a lot, but other functions have plenty of speed.

My installation uses 0% CPU with a raw image opened but not actually working on something. All 8 cores peg out during a export. This brings other operations to their knees.
Photo of Gavin Farrington

Gavin Farrington

  • 24 Posts
  • 2 Reply Likes
This reply was created from a merged topic originally titled LR Performance, Assign Preview/Export/Import/Move to lower-priority threads.

If I'm working in LR and running an (export / preview render / import / file move / metadata save / etc) then the user experience while interacting with LR degrades as these jobs demand more and more CPU resources.

For example, I'd like to be able to export images from one wedding, while starting color correction on another. Currently it's hard to use LR while exporting because the UI lags, sliders become less responsive, etc.

My idea would be to assign these kinds of non-realtime tasks to a separate thread that can run at a "below normal" priority, allowing me to continue working smoothly in LR.

My current only-kinda-workaround is to go into processes on my task manager, and assign Lightroom.exe the "below normal" priority. At least this way I can queue up a bunch of tasks, then go to a different app such as PhotoMechanic and get some things done there. Of course this still doesn't let me continue working in LR itself.
Photo of Moritz Rennecke

Moritz Rennecke

  • 4 Posts
  • 0 Reply Likes
This reply was created from a merged topic originally titled Lightroom - Paused export would improve workflow.

The ability to pause one or all running exports would be great. When exporting a wedding I have often 12 or more parallel exports. Since the running exports drain the cpu it takes time and nerves to start the other exports and continue editing is out of the question.
It would be wonderful if I could pause all exports and keep working until the evening or a break. Then start everything and the computer can work when I'm not working on it.

It would be a major improvement for the everyday workflow!
Photo of Ed

Ed

  • 3 Posts
  • 1 Reply Like
I used to be able to run multiple exports, but with 2015CC, I can never get to the second one until the first is finished. It tales me a lot more time sitting there waiting for my pc to respond so I can do the next export rather than queueing them up and letting them run while I work on something else. Something is wrong here, it should not hog all cpu just exporting 4 or 5 images.
Photo of Moritz Rennecke

Moritz Rennecke

  • 4 Posts
  • 0 Reply Likes
I'm not sure why my post was joined with this. I asked for a future possibility to pause/queue exports. That was more of a solution to this post since I can start multiple exports (sometimes up to 16) parallel. Of course I can't work in the development module anymore with an export under way. For that it would be nice to pause exports.

I use a macbook pro late 2012 (2,6 GHz i7, 16 GB RAM) and LR works fine with it.
Photo of Miguel Dias

Miguel Dias

  • 1 Post
  • 0 Reply Likes
LR really needs some deep review in speed and loads.

The performance for this last version is just horrible compared to LR5, will wait the current sync ends to roll back on 5, worst LR release ever, hope to see a update fix this.
Photo of joerg kastrup

joerg kastrup

  • 4 Posts
  • 0 Reply Likes
Does anyone know how to roll back a CC Version? I can't find how to select an earlier version in this CEF Tool or whatever that's called.
Photo of joerg kastrup

joerg kastrup

  • 4 Posts
  • 0 Reply Likes
Victoria, you made my day, thank you very much, that worked great!!!

The old version of LR6 is lightyears faster.
Photo of nigel wallace-iles

nigel wallace-iles

  • 11 Posts
  • 3 Reply Likes
Thank God it's not just me! I've been doubting my Hardware for a couple of weeks thinking there must be something wrong. i7 with 16gb of RAM shouln't be lagging like this. I thought it might be my new 5DR Raw files causing the problem. I really cannot believe how slow this LR6 is! I cannot work with this. I've got 10 shoots with around 6000 files to edit for my client and this is just unmanageable!
Adobe, can you just PLEASE add the 5DR Raw profile to LR5 so I can actually work! I feel like it's 1998!
I don't use CC, just the LR6 program - are there any updates or anything I can do to help at least while you guys work on a fix?
Photo of nigel wallace-iles

nigel wallace-iles

  • 11 Posts
  • 3 Reply Likes
Latest installed update is 6.3
Photo of Denni Russel

Denni Russel

  • 44 Posts
  • 9 Reply Likes
Try downloading the adobe dng converter (it's free). That will let you get a manageable file type out of the 5dr cr2s. You should be able to use LR 5 then. It's ads an extra step to your workflow, but it still might be faster than 6!
(Edited)
Photo of nigel wallace-iles

nigel wallace-iles

  • 11 Posts
  • 3 Reply Likes
Thanks Denni, it seemed that the 6.3 update resolved things, at least for the last hour or two. Then all of a sudden my CPU shot up to 80-90% with my RAM at 60%! Task manager shows that it is JUST LR6 causing the issue. I think my laptop is going to have a coronary! I'll take a look at the dng converter, just never had to in the past. Thanks for the swift reply and help.
Photo of Denni Russel

Denni Russel

  • 44 Posts
  • 9 Reply Likes
No worries! This stuff if driving me nuts, too. I teach photography at a college where we've got the very latest and fastest Mac pro desktops. My students are sitting there, twiddling their thumbs for half the class (or longer). And the school refuses to role back to LR5! I'm actually rewriting my entire course for next semester to exclude Lightroom. The performance issues coupled with the (now replaced) 'new' import dialogue have me really worried. We're trying to negotiate Capture One for our systems for next year. We obviously can't rely on Adobe anymore. Ugh.
Photo of nigel wallace-iles

nigel wallace-iles

  • 11 Posts
  • 3 Reply Likes
Great shame. I have no idea what the heck Adobe are doing. I had to upgrade to LR6 just because of the new RAW's in the 5DS. Was quite happy with LR5 as the extras in LR6 are not really game changers are they?! Hope you get it sorted too. Currently uploading 725 5mb jpegs to Photoshelter via LR6 - 1hr45min and still at 75%!!!!! Not looking forward to exporting the Tiffs!! Might go on holiday!
Photo of em vaningen

em vaningen

  • 68 Posts
  • 6 Reply Likes
Dear LIGHTROOM people. Can somebody PLEASE reply to the distressed users.

LR6.1 performs reasonable on my desktop, but no 6.x version does well on my laptop.

Why can NIKON display a full size NEF file in less than a second and why does it take LR up to 10 seconds ?

I have thousands of pictures of my last trip and cannot afford days of wasting my time.

Please do not ignore us. At least give a reply.
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 4676 Posts
  • 1797 Reply Likes
em, have you installed 6.3 which was released a couple of days ago? It should have solved this export issue. Of course, if you're having issues with general slowness, you may have a different problem entirely.
Photo of em vaningen

em vaningen

  • 68 Posts
  • 6 Reply Likes
I have created a new topic, for performance, without running anything else.
Photo of em vaningen

em vaningen

  • 68 Posts
  • 6 Reply Likes
Yes Victoria (and wow, thank you for your super quick reaction).

I have been posting in a wrong subject I fear.

My display comment relates to both library and develop view, without export or any other programms running on W10
Photo of Moritz Rennecke

Moritz Rennecke

  • 4 Posts
  • 0 Reply Likes
Can't understand the described hard core slow performance of LR CC 2015.3

I do have issues when doing like 10 Exports simultaneously but without running Exports my LR is doing its job just fine. (Thats why I asked Adobe to implement a pause-function for Exports.) I can work on my pictures in normal speed (Development Module, Radial Filter, ...) and also the Export is at the normal speed.
And fortunately they just returned to the older, better import screen.

I use a 15" MacBook Pro Retina Late 2012 (2,6 GHz i7 16 GB Ram).
Photo of James Robins

James Robins

  • 3 Posts
  • 1 Reply Like
I've been having general performance issues since the 2015.2.1 upgrade, including the thumbnails in Library view taking forever to render. I tried reverting to older versions with no luck... BUT I just deleted my previews file " Previews.lrdata and restarted lightroom... problem fixed! I then regenerated standard previews and problem remains fixed!
Photo of Martin Forster

Martin Forster

  • 2 Posts
  • 0 Reply Likes
I've been having the same issues as well since the lr6 update but today its has got so bad it is virtually unusable in develop mode. Its also acting quite oddly - creating temporary folders with one image at time on my hardrive and showing import photos in library in the wrong order and at times upside down. I've just downloaded the November update (not sure of the version number) so I will see how this goes

New update is even worse. 10-15 seconds delay is switching between images in develop mode. WTF??
Photo of Martin Forster

Martin Forster

  • 2 Posts
  • 0 Reply Likes
When I have checked my hard drive I still seem to have lightroom 5. Lightroom 6 looks like it has just been added alongside it. 5 runs fine as well so I'm just going to go back to that again.

If isn't sorted soon I'll be switching to Capture One
Photo of WestSideRailways

WestSideRailways

  • 14 Posts
  • 0 Reply Likes
thought it was the new version of windows10 that was the problem, untill i found this chat.
downloading a new version as i type, will have to wait and see what happens when finished.
Photo of WestSideRailways

WestSideRailways

  • 14 Posts
  • 0 Reply Likes
at the moment the new version is better then the old.
last couple of days i have had LR & PS & several pages of chrome open and open element(website making program) all open at the same time and have had no problems.
Photo of Elaine Costa

Elaine Costa

  • 1 Post
  • 0 Reply Likes
I have the same problem. absurd crashes. someone found the solution?
2TB SSD RAID 0

Photo of Jeffrey Tranberry

Jeffrey Tranberry, Sr. Product Manager, Digital Imaging

  • 15071 Posts
  • 2131 Reply Likes
What does the event viewer say the faulting module is? Is Lightroom up to date? https://helpx.adobe.com/lightroom/kb/keeping-lightroom-up-to-date.html
Photo of Bobby Hicks

Bobby Hicks

  • 8 Posts
  • 3 Reply Likes
I have found more that a couple times now when Lightroom 6 2015.5 slows down, I can do a system restore to an earlier date and it speeds up again. Can not explain why but at times I can just click on a thumbnail in develop module and start counting and get up to 3 before it opens. That in turn also slows down slider response too. Do a restore and I'm back to flying speed again. I'm about ready to go back to old lightroom without cc and old cs5 as I had none of this before cc. 
Photo of Sigurdur Ragnar

Sigurdur Ragnar

  • 54 Posts
  • 17 Reply Likes
i have tried everything. bought a new ssd and installed nothing other than lr cc and it is slow as hell. I have a performance machine that should eat this thing up and it is so slow! killing me! taken so much time waiting for this darn thing to work and looking for workarounds, please adobe help out!!!
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 4676 Posts
  • 1797 Reply Likes
You're going to need to be very specific about exactly what is slow.

Also tell us how many smart collections you have and how big they are?
Photo of anssik

anssik

  • 140 Posts
  • 30 Reply Likes
@victoria: are Smart Collections slowing down LR? I have 29 smart collections myself and about to start using many more of them, BUT if LR slows down because of them I have to rethink.
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 4676 Posts
  • 1797 Reply Likes
I'm not entirely sure, but it's a theory I'm investigating.  I've been testing a 1.3 million photo catalog (which is admittedly far bigger than most!) and they are slowing down metadata updates in that catalog, but it's a pretty unusual situation.  Just one to rule out though.  Easy way to test is to close the Collections panel and restart LR - that way they don't start counting, which seems to be the slow down.
Photo of Sigurdur Ragnar

Sigurdur Ragnar

  • 54 Posts
  • 17 Reply Likes
Hey. When I click to move to next photo it takes about 5sec to move and tender preview. When in develop module and I hit g to move to library can take forever. When in develop module hitting r to crop or rotate takes 10 to 15 SEC To Be ready. Forget to try while export is working. No smart libraries. Small catalog. I have tried everything incl. A new ssd, uninstalling, everything.
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 4676 Posts
  • 1797 Reply Likes
That's definitely not normal Sigurdur. Tell us your full system specs and also where your catalog is stored (e.g. SSD, spinning drive, etc.)
Photo of Sigurdur Ragnar

Sigurdur Ragnar

  • 54 Posts
  • 17 Reply Likes
I7 32gb ddr3 GTX780 catalog on Samsung evo 500gb c: drive
Thanks for thinking on this with me
(Edited)
Photo of Jeffrey Tranberry

Jeffrey Tranberry, Sr. Product Manager, Digital Imaging

  • 15071 Posts
  • 2131 Reply Likes
Is graphics card driver up to date? Is there also an Intel integrated graphics card in this system?
Photo of Sigurdur Ragnar

Sigurdur Ragnar

  • 54 Posts
  • 17 Reply Likes
after spending 3 hours editing an hour long job last night and trying all kinds of things i found something. not sure if this is a permanent fix or if this is a pie in the sky but an amazing difference for now. 
In the NVIDIA settings i found this,

under that cuda I selected to use the graphics card not the global settings. even if the global settings are set for the card.
im not even all that sure what this does since I have no idea what all that is, I dont even speak English :)  but so far this looks to be a life saver
(Edited)
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1533 Posts
  • 495 Reply Likes
Lightroom does not use CUDA. I am not sure why it makes a big difference for you. Probably it has something to do with the GPU driver behavior. Glad that you figure it out.

Can you confirm that the your earlier performance issue is only present when the GPU acceleration is turned on in the Lightroom user preference. When you turned the GPU acceleration off, the performance is ok?
(Edited)
Photo of Sigurdur Ragnar

Sigurdur Ragnar

  • 54 Posts
  • 17 Reply Likes
hey, 
yea not sure why this is but so far so good.
it did not matter if i turned it on or off before, I tried both and both ways super slow.

I have not gotten the message that direct2d is not working since I changed that cuda thingy.
Photo of Sigurdur Ragnar

Sigurdur Ragnar

  • 54 Posts
  • 17 Reply Likes
i celebrated to quick :( still slow and painful. does not seem quite as bad as before but unacceptable. Looking at PhaseOne seeing if that might be something better. 
Photo of nigel wallace-iles

nigel wallace-iles

  • 11 Posts
  • 3 Reply Likes
Same problem mate. Look at ON1 software.
Photo of Sigurdur Ragnar

Sigurdur Ragnar

  • 54 Posts
  • 17 Reply Likes
yea I looked at on1 and i need something more robust for batch editing. I edit and deliver large numbers of photos. 

so frustrating and no help at all from adobe, no suggestions or acknowledgment of this shitty situation.  another sad company focused on the masses of people that just play around and ignore people who make a living from this, I guess we are fewer and not as lucrative market for them when they can sell this to families and dabblers.
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 4676 Posts
  • 1797 Reply Likes
> no help at all from adobe, no suggestions or acknowledgment of this shitty situation

They're working on tracking it down, but it's proving hard to find at the moment. Rest assured, it's a high priority.
Photo of nigel wallace-iles

nigel wallace-iles

  • 11 Posts
  • 3 Reply Likes
They've had 10 months Victoria. I'm sure it's not that high a priority which is a great shame.
Photo of Sigurdur Ragnar

Sigurdur Ragnar

  • 54 Posts
  • 17 Reply Likes
yea this is super ridicules another 2.5hrs session that should have been an hour. so when my work quality dwindles and my sanity leaves me i wonder where Adobe will be then. Ohh they will just be selling their stuff to the 90% of people that edit one photo at the time and ignoring the rest of us. I have been using PS since the early 90's and have spent thousands of with then just to be left out to hang like this. 
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1533 Posts
  • 495 Reply Likes
@Sigurdur What changed between yesterday and now to explain the difference?

@Sigurdur @nigel The performance issues always tends to be specific to the individual situation (setup & workflow). The developers need to see the problem before they can fix it. The best way that you can help us tracking down the issue is to be as specific as possible when describing the problem.

1) For starters, please post the Lightroom>Help>System Info..., this will give us a baseline info about your machine configuration.
2) Then describe in detail steps in Lightroom to reproduce the issue that you are reporting. Think of any of special setups or workflows that could make your situation different from others. Our QE or others might have miss those test cases or setup.
3) Experiment within your same setup to see if you can find a particular pattern.
4) If you have access to a secondary machine, see if you can reproduce the issue there following the same steps.
(Edited)
Photo of Sigurdur Ragnar

Sigurdur Ragnar

  • 54 Posts
  • 17 Reply Likes
hey,
thanks for reading in this for me!!!!
nothing has changed. it just slowed down. so here is my sob story,
lightroom starts messing up couple of months back.
I reinstalled it. 
i bought a new ssd just to be sure it was not that, did not migrate my old stuff just in case, just installed windows 10pro, drivers and cc, lightroom still super slow.
tried to start a new catalog, put the catalog on the ssd, put it on the old (now fresh formatted) ssd, catalog and setting in all kinds of locations.
during import tried smart preview, full preview and minimal all the same.
i have everything off, face location and mobile.
there does not seem to be any difference in if I have the edit/settings/performance set to use graphics processor or not

so the issue, when i click arrow or next image in catalog it can take as much as 5 sec to switch to next image, then it can take up to 10 sec to render preview and then when I past settings from previous image that can take 10 sec to preview. if I need to use tools like brush, spot healing or any overlay tool it takes for ever. the spot healing tool will sit for a while then when I click on the spot to move it for a better sample it staggers, jumps and takes forever. with paint brush, i paint like mad over what I need then wait 5-10sec for the adjustment to paint in. i can watch as the paint head moves over the image and applies the adjustment. when i hold down alt to remove a section it does the same, slow moving and staggers along.

there is nothing I can do if lr is exporting or importing, converting to dng or any other long process, then everything is way way slower from already super slow performance, so now I have to set my machine to upload my work overnight.
it now takes me 2-3 times longer to work than it should.
I have been in a bunch of forums and read a lot of descriptions from users with the same issue.
I work typically with about 80-150 photo size project. 
I shoot with D800's, d7000's d2xs, sony ar7ii' and 7ii,, dji drones, gopros  and it does not look like any difference in performance. 

I am not even going to talk about video playback performance! it is just a joke, might as well be drafting my work with a crayon and paper.

sorry for the long post!
and thanks for the help!

Lightroom version: CC 2015.6 [ 1078672 ]License: Creative Cloud
Operating system: Windows 10
Version: 10.0
Application architecture: x64
System architecture: x64
Logical processor count: 8
Processor speed: 3.4 GHz
Built-in memory: 32713.8 MB
Real memory available to Lightroom: 32713.8 MB
Real memory used by Lightroom: 433.3 MB (1.3%)
Virtual memory used by Lightroom: 395.5 MB
Memory cache size: 226.1 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) 2560x1600, 2) 3840x2160
Input types: Multitouch: No, Integrated touch: No, Integrated pen: Yes, External touch: No, External pen: Yes, Keyboard: No

Graphics Processor Info: 
GeForce GTX 760/PCIe/SSE2

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


Application folder: C:\Program Files\Adobe\Adobe Lightroom
Library Path: E:\May 2016\May 2016.lrcat
Settings Folder: C:\Users\Siggi\AppData\Roaming\Adobe\Lightroom

Installed Plugins: 
1) Canon Tether Plugin
2) Export to Photomatix Pro
3) Facebook
4) Flickr
5) HDR Efex Pro 2
6) jf Zenfolio
7) Leica Tether Plugin
8) Nikon Tether Plugin

Config.lua flags: None

Adapter #1: Vendor : 10de
Device : 1187
Subsystem : 27653842
Revision : a1
Video Memory : 1989
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: Uninitialized
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 760/PCIe/SSE2
GL_SHADING_LANGUAGE_VERSION: 4.50 NVIDIA
GL_STENCIL_BITS: 8
GL_VENDOR: NVIDIA Corporation
GL_VERSION: 4.5.0 NVIDIA 368.39
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 Sigurdur Ragnar

Sigurdur Ragnar

  • 54 Posts
  • 17 Reply Likes
work flow,
I import raw files, second copy goes on to a drop drive and one copy in the catalog. the current catalog is drive e: 7800rpm 1tb internal sata drive, lightroom is on c: with scratch and cash folders. I have tried this on a ssd sata or on the c: drive, then typically I apply a basic adjustment to a batch of photos and then I go over them one by one, lot of copy and paste settings from one image to another. then when Im done with editing i drag the folder to an external file station.
current catalog has two active folders and then a bunch of folders on the diskstation.
i have tried to make new catalogs and keep them in different locations. 
curre
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1536 Posts
  • 496 Reply Likes
@Sigurdur Thanks. Clearly something is not quite right. Try:
1) Turn off the use of the second monitor in Lightroom to see if it helps;
2) Try disable the 3rd party Lightroom plug-ins from Lightroom File>Plug-in Manager...

When the slow down happens, what is the memory usage of Lightroom according to the Activity Monitor? 
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1536 Posts
  • 496 Reply Likes
Since we're shooting in the dark here, I'd like to collect some log files from you to get some clue. Please follow the following instructions:

A) Locate the LR configuration folder
    1) Launch LR
    2) "Edit>Preferences..."
    3) Select Preset tab
    4) Click "Show Lightroom Presets folder"
    5) A Finder window will open with a folder like "/Users/your-login-account/Library/Application Support/Adobe/Lightroom/" selected. This is the LR configuration folder.
B) Copy the config.lua file into the Lightroom configuration folder. This config.lua file contains code that LR will read at startup to enable logging.
C) Restart LR. This will ensure LR reads the config.lua at start up.
D) Do the steps to reproduce your performance issue.
E) Quit LR
F) Go to your Documents folder (/Users/your-login-account/Documents/). You should see a bunch of recently created *.log files. Zip them and upload it to some online location (CC sync folder or Dropbox) and share the link with me at sichen at adobe dot com.

G) Disable logging by moving, deleting, or renaming the config.lua file. If you skip this step, LR will continue to append to these files and they will grow unbounded. So please remember to get rid of config.lua after the test.
Photo of Sigurdur Ragnar

Sigurdur Ragnar

  • 54 Posts
  • 17 Reply Likes
Hey,
the second monitor tab is off and I never use it 
the only 3r party plug in active is the export to zenfolio. on the last test I did where I installed it all clean on the ssd there were no addons and the only thing i did out of the normal clean install from cc was turn off face, location and mobile cc sync folder,
Photo of Sigurdur Ragnar

Sigurdur Ragnar

  • 54 Posts
  • 17 Reply Likes
thanks,
I sent you the config test folder.
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1533 Posts
  • 495 Reply Likes
Please don't send the zip file as attachment via the email. Our corporate email system will block such type of files. Please send a shared link via dropbox or Adobe CC Sync. Thanks.
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1536 Posts
  • 496 Reply Likes
From the screen cap, I see that you have a network drive \\DISKSTATION\, is that a NFS drive? What happens if you disconnect it temporarily, does it make a difference?
Photo of Sigurdur Ragnar

Sigurdur Ragnar

  • 54 Posts
  • 17 Reply Likes
hey,
that is a nfs it is for storage only i never work of that drive.
if I need something from there I move it the c:
I have tried to turn it off and to disconnect it from the network in case it was some kind of wired index issue.
on the last catalog install I used for part of the test I sent you it was not installed to that catalog. 
yea im sorry, you  did say dropbox and i e-mailed it :) I shared a dropbox with you :)
i don't have cc shared turned on and have not dared to even try to use it for fear of even more slow down.
Photo of Sigurdur Ragnar

Sigurdur Ragnar

  • 54 Posts
  • 17 Reply Likes
this is the tool panel of the last catalog used in the test. no sencondary apps, second screen off, no diskstation connected, no sharing, faces or locations. 
no
Photo of Denyer Ec

Denyer Ec

  • 55 Posts
  • 43 Reply Likes
I'm glad this is getting more attention. I've dumped LR CC Standalone  in favour of 5.7 as CC is unusably slow, regardless of whether an export is running or not.

It actually runs faster with GPU Accel turned off (hah!) but even then it's useless. 3-5 seconds to switch between images in the develop module, horrendous memory leakage (Have to reload the application every 30-50 minutes) and just overall sluggishness.

Intel 4790K @ 4ghz, 32gb RAM, nVidia 970 GTX and SSD's all around,  no network drives.

Logs here: https://1drv.ms/u/s!AnWpr2dszNA_gtNvQKqY41d30blBGQ
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1532 Posts
  • 494 Reply Likes
@Denyer Got the log. I will need to study it. BTW, Lr 6.6 introduced an optimization that will make walking photos in develop feel faster. Victoria's blog http://www.lightroomqueen.com/whats-new-in-lightroom-cc-2015-6-and-lightroom-6-6/ has a little bit more info.
Photo of Sigurdur Ragnar

Sigurdur Ragnar

  • 54 Posts
  • 17 Reply Likes
thanks for chiming in! sorry about you having issues, I hope there will be a solution! :)
yea my machine eats doom4 at 4k with no lag no refresh issues while watching soccer on the second monitor, not a computer hardware issue, might be some config thing!
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1532 Posts
  • 494 Reply Likes
@Sigurdur Could you post the link to your log files here as @Denyer did? The spam filter will do unexpected things :-).
Photo of Sigurdur Ragnar

Sigurdur Ragnar

  • 54 Posts
  • 17 Reply Likes
I am running the latest updated version of lr.
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1532 Posts
  • 494 Reply Likes
@Sigurdur Got the log.
Test the following in sequence:
1. Collapse the Detail Loupe view in the Detail Panel and make it not visible. 
2. Close the Navigator/Histogram/Filmstrip 

See if any of this helps.
Photo of Sigurdur Ragnar

Sigurdur Ragnar

  • 54 Posts
  • 17 Reply Likes
done,
still about 3-5 sec to move to the next image and if i then click zoom to 1:1 that takes another 3 -4 sec. spot healing tool still takes a long time and stutters like mad.
Photo of nigel wallace-iles

nigel wallace-iles

  • 11 Posts
  • 3 Reply Likes
Sigurdur , I am having EXACTLY the same issues and although my system isn't quite as advanced as yours, it's still an Intel i7 2ghz, 16gb ram and 7200hdd, it eats any other application and LR5 was a doddle on it. Ever since upgrading to LR6 standalone it has gone pear-shaped. I actually dred editing now and I currently have 3k images to edit for my client. Sigh.
Photo of Sigurdur Ragnar

Sigurdur Ragnar

  • 54 Posts
  • 17 Reply Likes
sorry to hear that Nigel. thanks for chiming in. maybe if more chime in with the same issue we get more attention. looking forward to what comes out of the test logs! once they figure this out it will be the same fix for us all, i hope. 
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1532 Posts
  • 494 Reply Likes
@Sigurdur Based on your provided logs, I think a few things contributed to your specific slow down:
1. The detail loupe render in the Detail Panel. You should collapse/hide the detail loupe view in the Detail Panel unless you really need it. The usefulness of this loupe is much less in the recent version of Lightroom because Lr now renders the sharpen and NR at all zoom level these days. In the early days, it was more of a performance workaround when the sharpen and NR are not rendered accurately if at all in zoom out view.

2. Your image size is big 7887x5260. What camera are they captured from?

3. There are apparently spot removal and local adjustment brushes applied to the photos. Those are known to be taxing to Lightroom if you have lots of them.
Photo of Sigurdur Ragnar

Sigurdur Ragnar

  • 54 Posts
  • 17 Reply Likes
lol so basically no help??
disable features that you put in there, blame it on spot healing and local adjustments that you hail as the "most advanced features of LR" and my file sizes?????
you guys are in for a rude awakening if you can't build software to support your own tools or the cameras that everyone is using!!!!!!
totally useless!!!!

in the folder that was in the test were Sony a7r ii files, d800 files and small dji drone files, it does not matter what gallery i am working on, small , medium or large files. LR just kind of hobbles on!
Photo of em vaningen

em vaningen

  • 68 Posts
  • 6 Reply Likes
Your story is saddening. I had the same issues (around a year ago) on the (smaller) computer I use when on travel in Europe.

Victoria B. will be happy to hear that my problems seem to have disappeared last time is started to use that computer. Not sure what caused it. I replaced disk with SDD, but I don't know about the effect of W10 and CC upgrades.

CC15.6 however did crash on me during a normal edit of a small jpg file. Atthis stage I am not worried about that.
Photo of Diko

Diko

  • 77 Posts
  • 9 Reply Likes
"2. Your image size is big 7887x5260. What camera are they captured from?

3. There are apparently spot removal and local adjustment brushes applied to the photos. Those are known to be taxing to Lightroom if you have lots of them."

So since I am intensively working with 5Ds (50 Megapixels) and because I use intensively Local adjusment brushes and spot removals I should move to Capture One? Is this what you are suggesting?
(Edited)
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1532 Posts
  • 494 Reply Likes
The team will continue to make performance that matters to the customers. Sometimes the issue is a little bit harder. Non-destructive parametric editing like those in Lightroom is great, but it also comes with some baggage. It means Lightroom has to render the image from the raw bits every time one makes an adjustment change. Certain edits are more expensive to compute than others. So it is a tradeoff.

If you found yourself to need to brush a lot or doing a lot of spot removal corrections on a particular photo, you could consider whether you should make the change in Photoshop where you don't need to carry all the edits forward.
Photo of nigel wallace-iles

nigel wallace-iles

  • 11 Posts
  • 3 Reply Likes
Hello LR Gurus,

i am having pretty much the same problems as Sigurdur Ragnar, above. Here is my System Info Log.

I feel like crying when I need to edit my 1000's of images. I feel so disheartened when I open up LR now. I never felt like this. I always sang its praises and ALWAYS recommended it to everyone I came into contact with photographically. I've looked at Capture 1 and even downloaded it. I am loathe to try it though as I really don't have the time to re-learn another editing suite. I've been on LR since the beginning!

Please help. Plese don't recommend that I go into PS to do my editing. I have 1000's of images from many shoots to edit. That is why I've always used LR. Because I'm a photographer, not a designer!

Lightroom version: 6.6 [ 1078672 ]License: Perpetual
Operating system: Windows 7 
Version: 6.1
Application architecture: x64
System architecture: x64
Logical processor count: 8
Processor speed: 1.9 GHz
Built-in memory: 16361.1 MB
Real memory available to Lightroom: 16361.1 MB
Real memory used by Lightroom: 4911.9 MB (30.0%)
Virtual memory used by Lightroom: 5024.8 MB
Memory cache size: 4136.8 MB
Maximum thread count used by Camera Raw: 8
Camera Raw SIMD optimization: SSE2,AVX
System DPI setting: 120 DPI
Desktop composition enabled: Yes
Displays: 1) 1920x1080, 2) 1920x1080
Input types: Multitouch: No, Integrated touch: No, Integrated pen: Yes, External touch: No, External pen: Yes, Keyboard: No

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

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


Application folder: C:\Program Files\Adobe\Adobe Lightroom
Library Path: C:\Users\nigel\Pictures\Lightroom\LR BackUp\2011-04-13 0008\Backups\2015-08-12 2222\Files for Editing-2-2-2.lrcat
Settings Folder: C:\Users\nigel\AppData\Roaming\Adobe\Lightroom

Installed Plugins: 
1) ON1 Resize 10
2) PhotoShelter

Config.lua flags: None

Adapter #1: Vendor : 10de
Device : dd1
Subsystem : 71001558
Revision : a1
Video Memory : 1489
AudioDeviceIOBlockSize: 1024
AudioDeviceName: Headphones (High Definition Audio Device)
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 460M/PCIe/SSE2
GL_SHADING_LANGUAGE_VERSION: 4.50 NVIDIA
GL_STENCIL_BITS: 8
GL_VENDOR: NVIDIA Corporation
GL_VERSION: 4.5.0 NVIDIA 368.22
GPUDeviceEnabled: false
OGLEnabled: true
GL_EXTENSIONS: GL_AMD_multi_draw_indirect GL_ARB_arrays_of_arrays GL_ARB_base_instance GL_ARB_blend_func_extended GL_ARB_buffer_storage GL_ARB_clear_buffer_object GL_ARB_clear_texture GL_ARB_clip_control GL_ARB_color_buffer_float GL_ARB_compatibility GL_ARB_compressed_texture_pixel_storage GL_ARB_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_separate_shader_objects GL_ARB_shader_atomic_counter_ops GL_ARB_shader_atomic_counters GL_ARB_shader_bit_encoding 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_NV_robustness_video_memory_purge 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_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_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_NV_shader_thread_group 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 Stefan Redel

Stefan Redel

  • 88 Posts
  • 29 Reply Likes
Just go back to LR CC 2015.5.1 - it works!
Photo of WestSideRailways

WestSideRailways

  • 14 Posts
  • 0 Reply Likes
isn't what Photoshop is for to do edits..?!!

any edits i do in photoshop and do not have any problems

LR in my opinion is not meant to replace Photoshop. 
(Edited)
Photo of nigel wallace-iles

nigel wallace-iles

  • 11 Posts
  • 3 Reply Likes
Not with Canon 5DS files!
Photo of Denni Russel

Denni Russel

  • 44 Posts
  • 9 Reply Likes
Re the suggestion that you use Photoshop - Photoshop is most certainly NOT for editing large numbers of images. LR is. That's kinda the whole point... Anyone who would choose to edit 1000's has, obviously, never tried to do so. Even with the horrendous slow downs in LR 6, it's still weeks faster than editing in PS would be. Nigel was right to ask that any PS suggestions be left unsaid.

I gotta say, I'm back to editing in LR 5.7. I can not work in LR6 when dealing with volume. It is prohibitively slow. I'm beyond sick and tired of Adobe bs-ing  us all about this. I teach at two colleges and one university. I use A LOT of different computers. LR 6 is measurably slower on every single one. Without fail. 

Are you able to roll back to LR 5?
Photo of Denyer Ec

Denyer Ec

  • 55 Posts
  • 43 Reply Likes
Absolutely sick of this - Trying to edit a 300 shot set, WB slider is so laggy there's a 2-3 delay between adjustments. Going to try 5.7 as this current CC build is completely unusable.
Photo of nigel wallace-iles

nigel wallace-iles

  • 11 Posts
  • 3 Reply Likes
I Can't use 5.7 anymore as it's not compatible with Canon 5DS RAWs. I just tried editing a few images in LR. My RAM went up to 7GB and 80% CPU and when I tried to spot heal something very simple, well, that was it - the death knell! My clients are screaming at me for these images. I just do not know what to do! I'm going to lose my main client which generates 70% of my income because of this. Just devastated that Adobe are not addressing this with any expedience. WE ARE DEAD IN THE WATER!
Photo of Sigurdur Ragnar

Sigurdur Ragnar

  • 54 Posts
  • 17 Reply Likes
Total bummer. The suggestions from Adobe to not use the tools in the program, smaller files and export 100's of photos to ps is basically a professional suicide.
Photo of Sigurdur Ragnar

Sigurdur Ragnar

  • 54 Posts
  • 17 Reply Likes
Total bummer. The suggestions from Adobe to not use the tools in the program, smaller files and export 100's of photos to ps is basically a professional suicide.
Photo of Denyer Ec

Denyer Ec

  • 55 Posts
  • 43 Reply Likes
I'm in the same boat, currently re-importing a set I thought I'd edit in CC into 5.7 (Fortunately my D800 is supported) because the client wants the proofs today and I'm miles away from getting them out.

Phocus from Hasselblad has support for my camera so I'm going to give that a look, especially given that it's free. I just feel rather galled at having paid for the standalone licence for LR 5.7 and then CC, that I'm neither elegible for a refund nor able to save myself the expense by cancelling a subscription :/
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 4676 Posts
  • 1796 Reply Likes
Guys, there's no need to go all the way back to 5.7 if you're having trouble with the latest update. Just roll back to 6.5.1, or whatever version you were happily using until last week. http://www.lightroomqueen.com/how-do-i-roll-back-to-lightroom-2015-1-1-or-lightroom-6-1-1/
Photo of Denyer Ec

Denyer Ec

  • 55 Posts
  • 43 Reply Likes
Fair, however I (And I'm assuming others above) have not been happy with any release of CC to date, since installing the standalone version shortly after release.
Photo of Denni Russel

Denni Russel

  • 44 Posts
  • 9 Reply Likes
Re Victoria Bampton's comment: Every version of 6 is slower than 5.7 - so... that doesn't work. We've been having these problems since release. While there has been a slight speed increase since initial 6/CC release, it's simply not useable for far too many people.

Nigel, what about the DNG converter? You could use that to convert the 5Ds files, then edit in an older version of LR. I'm feeling for ya!
Photo of Sigurdur Ragnar

Sigurdur Ragnar

  • 54 Posts
  • 17 Reply Likes
this has been longer than just the last update. 
im now working on another gallery that should have taken about 2 hours and I am in my 5th hour of editing. I guess i could just do what adobe does and dont give a crap about my customers and just put out crap? not!!!! im out!!!!!!
Photo of Sigurdur Ragnar

Sigurdur Ragnar

  • 54 Posts
  • 17 Reply Likes
it took lr the whole second half of the amazing game between Iceland and Austria to upload 146 images to a dropbox folder fron dng at 14 inches long side at 300dpi... I know I should be uploading them at 4x5 inches at 72dpi in black and white, I know all my fault!!!! LR is awesome and I suck with all my dpi's, big files and adjustment tools!!!

and adobe totally silent other than telling me to close panels, not use tools and smaller files?????
Photo of Sigurdur Ragnar

Sigurdur Ragnar

  • 54 Posts
  • 17 Reply Likes
AAAAAAAAAAAAAAAAAAAAAAAARRRRRRRRRRRRRRRRRRRRRRRGGGGGGGGGGGGGGGGGGGGGGGGG!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Photo of Stefan Redel

Stefan Redel

  • 88 Posts
  • 29 Reply Likes

Agreed. :)


Just go back to CC2015.5.1...

Photo of Sigurdur Ragnar

Sigurdur Ragnar

  • 54 Posts
  • 17 Reply Likes
you have to be kidding!!!!!!
I have a gallery with 700 photos to go through! 
see when I click on the next image how long it takes, the slider lags like mad.
and this is in a tiny minimized for capture window so it does not even have to render full frame!!

#adobe are you guys even looking a this or you just going to keep blaming for for using your tools and for taking too many too big images??????
(Edited)
Photo of Stefan Redel

Stefan Redel

  • 88 Posts
  • 29 Reply Likes

Same here. Downgrade to 2015.5.1 takes approx 10 minutes. It is REALLY easy.

Then you're able to do your work again.

I guess that the Adobe-representatives doesn't know what's really going on. Capture One gets very sexy! But... It lacks of a history. Hmpf.

Photo of Sigurdur Ragnar

Sigurdur Ragnar

  • 54 Posts
  • 17 Reply Likes
I can't figure out how to backgrade this thing
Photo of Stefan Redel

Stefan Redel

  • 88 Posts
  • 29 Reply Likes
Google... Victoria mentioned it above... Adobe...

OK, the short one: http://www.lightroomqueen.com/how-do-i-roll-back-to-lightroom-2015-1-1-or-lightroom-6-1-1/
Photo of Sigurdur Ragnar

Sigurdur Ragnar

  • 54 Posts
  • 17 Reply Likes
thanks Stefan Redel!!!! i think i might be a little bit in love with you, might just be like a fascination transfer from laggy buggy lr but thanks you are awesome and Victoria for posting the directions for that downgrade. not awesome but vastly better!!! I might keep my job!! at least my senses, for now :)
Photo of Stefan Redel

Stefan Redel

  • 88 Posts
  • 29 Reply Likes
:D
Photo of Tomislav Ćuto

Tomislav Ćuto

  • 2 Posts
  • 0 Reply Likes
Hello to all of you,

One week ago I bought new MacBook 12" Retina (1,2 Ghz m5, 8GB RAM, 512 SSD) and today i finally try some Time lapse editing in Lightroom version: CC 2015.6 [ 1078672 ]

Generally, everything is ok, but the export process is painfully slow. My 495 pictures LR is exporting almost two hours. On my iMac 27" (i5, 32GB RAM, 1TB 7200 HDD) 600 photos are exported in 20 minutes or less. I know that in iMac there is 32GB RAM according to 8GB in MacBook, but I think that this kind of slowness isn't norml. On iMac i have previous version of Lightroom. 

I tried check/uncheck "Use Graphic Processor" option, but everything is same. 

Do you have any suggestions? It's not a "life problem" for me, I still can edit my Time lapses on iMac, but I just want to know that this is not a hardware problem in my MacBook. 

Thanks in advance.
Photo of Sigurdur Ragnar

Sigurdur Ragnar

  • 54 Posts
  • 17 Reply Likes
if you are on the latest version of LR I would use the link and help outlined in a previous comment and install a previous version of lr. not sure how much that will help with the export speed but interface sure will be more responsive. I do a 600-700 photo export to dropbox inches on the long  side, 300dpi jpg in about an hour or so. 
i have a macbook pro with 8gb of ram and an ssd and it is much faster with the old version of lr.
Photo of Tomislav Ćuto

Tomislav Ćuto

  • 2 Posts
  • 0 Reply Likes
Thanks for reply. 
I don't have any issues with workflow in LR, just in export process. Interface is smooth and very responsive, just like on my iMac. But, on iMac exporting is much faster, that's strange for me, because in MacBook I have SSD, and in iMac is "ordinary" SATA disk. Ok, memory is much, much "harder" on iMac, 32 GB compared with 8 GB in MacBook, but I think that this kind of slowness isn't normal...
Photo of em vaningen

em vaningen

  • 68 Posts
  • 6 Reply Likes
I am on the latest release, and after horrific problems initially, I have stable and good performance on my desktop and even on my, initially slow, laptop.

M Q's:
1. Did I miss any involvement of Adobe in this thread. ?
2. We all know that filesize is expressed in bits, bytes, etc. What is the point of a discussion mentioning inches and DPI, the latter only relevant when we print?
Photo of Sigurdur Ragnar

Sigurdur Ragnar

  • 54 Posts
  • 17 Reply Likes
adobe was on here and asked for recording of some test files, then told us to close the panels in lr, that I was using too many local adjustments and files large. since then nothing.
the question had been on exporting being 
Photo of em vaningen

em vaningen

  • 68 Posts
  • 6 Reply Likes
My files are approx 45MB. and i have no idea why my problem has gone away. I do use 1:1 previews. Did you  try that ?
(Are you from beautiful Iceland Sigurdur?)
Photo of Sigurdur Ragnar

Sigurdur Ragnar

  • 54 Posts
  • 17 Reply Likes
yea my files are from D800 and sony a7rII and are big, I had to go back to older version.
I use standard previews, I have tried minimal, smart but not 1:1.

yea im Icelandic. I live in Texas now. :)
Photo of em vaningen

em vaningen

  • 68 Posts
  • 6 Reply Likes
Victoria suggested 1:1 to me. it's the only change I made.
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1536 Posts
  • 496 Reply Likes
@Sigurdur Watched your recorded video on walking images in develop. It is helpful to see what you are experiencing on your machine (I see that it is a Windows box). I assume you still has the same system setup as you reported before. When you toggle to the next photo, I don't see the Lightroom popping up the "Loading..." bezel as it does in the earlier version of Lightroom. That is good because that is one  optimization we added to CC 2015.6/6.6 to make the walking the photos in the develop (in a normal pace) feel more snappy. Your video shows some hesitation doing the switch. That does not seem to be normal when the next negative have been preloaded by Lightroom in your case.

In your recorded video, do you have the GPU acceleration on or off? I would check to make sure that your GPU driver is up-to-date, you have enough video RAM for the GPU card and it has enough data throughput (speed to transfer data from the CPU memory to the GPU memory) to handle the big image that you throw at it. I realize you have a 3-year old GTX 760 card (https://en.wikipedia.org/wiki/GeForce_700_series).

One question, if you walk adjacent photos A->B, and then try switch from B->A, is the switch more instantaneous than the initial switch from A->B?
Photo of Sigurdur Ragnar

Sigurdur Ragnar

  • 54 Posts
  • 17 Reply Likes
hey,
the drivers are up to date. gpu is set to on. it is faster going b-a to a loaded image than it is a-b to a new image.
I have 32gb of ram the card is a 
after downgrading it is faster. 
ps on pen input and all edits is lighting fast and I never have issues there, using the latest updated version.

then there is this line?
"Memory cache size: 0.0 MB"    ??????????

In system settings lr is seeing my system as win 8.1? i have win 10, latest version.

Lightroom version: CC 2015.1.1 [ 1032027 ]License: Creative Cloud
Operating system: Windows 8.1 Home Premium Edition
Version: 6.3 [9600]
Application architecture: x64
System architecture: x64
Logical processor count: 8
Processor speed: 3.4 GHz
Built-in memory: 32713.8 MB
Real memory available to Lightroom: 32713.8 MB
Real memory used by Lightroom: 2125.6 MB (6.4%)
Virtual memory used by Lightroom: 2223.6 MB
Memory cache size: 0.0 MB
Maximum thread count used by Camera Raw: 4
Camera Raw SIMD optimization: SSE2
System DPI setting: 96 DPI
Desktop composition enabled: Yes
Displays: 1) 2560x1600
Input types: Multitouch: No, Integrated touch: No, Integrated pen: Yes, External touch: No, External pen: Yes, Keyboard: No
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1536 Posts
  • 496 Reply Likes
This seems to be a different (older?) system than the more capable Windows 10 system that you posted earlier.

>"it is faster going b-a to a loaded image than it is a-b to a new image"
This means the data bandwidth/throughput of your GPU card (CPU RAM-> GPU video RAM) might be the weakest link for this particular machine setup. You might consider upgrade to a more capable GPU to see if it helps. You might as well turning the GPU acceleration off on this machine.

"Memory cache size" keeps track of the size of some internal cache which can be purged once a while. Does this number always remains at 0 for you, even after some Lightroom use?
Photo of Sigurdur Ragnar

Sigurdur Ragnar

  • 54 Posts
  • 17 Reply Likes
this is the same computer as last time time I posted! ill keep an eye on that cash but it has been a while (few hours of work) since I emptied it
Photo of Sigurdur Ragnar

Sigurdur Ragnar

  • 54 Posts
  • 17 Reply Likes
this system eats anything with out issues!!! lightroom has not been an issue since the last few weeks.
Photo of nigel wallace-iles

nigel wallace-iles

  • 11 Posts
  • 3 Reply Likes
I'm just doing the retrograde to 6.5.1 and hoping this resolves my issues for now. Just back from 5 days of work in the Lake District for client and have 1800 images to go through. Please, please be ok! Fingers crossed!
Photo of Sebastian Weg-Erbauer

Sebastian Weg-Erbauer

  • 1 Post
  • 0 Reply Likes
i hate it, i have a AMD threadripper 16 cores , 32gigs of ram and a GTX 1080 and lightroom cc classic lags like hell. when i work and have my resource monitor open, nothing realy is going on there, RAM is on 20% , CPU is on 10-20 %. it makes me crazy when i start a project with a couple of 100 pix and during editing lightroom starts to slow down and gets a lot of latency... :/
(Edited)