Skip to main content
J
jonhob
Participating Frequently
May 16, 2023
Question

M1 MBP slow performance

  • May 16, 2023
  • 4 replies
  • 471 views

I have a 2021 16" M1 MBP with 16GB RAM and 252.13 GB available of 494.38GB drive. I don't normally shoot RAW so all my images are 20MB JPGs off a Nikon D5. The main use of my laptop is live editing at a football match and they are cleared off after each match however I occasionally cover events where I may shoot up to 3-4k images and use Lightroom to cull the rubbish and do very basic edits like crop and straightening.

 

My issue is when I scroll through the files in the develop module after 7-8 images I get the spinning beach ball. As you can imagine, it's driving me mad and I'm getting to the point I want to ditch Lightroom altogether. I really have no idea what is causing the lagging. 

 

Has anyone got any idea how I can sort this issue?

 

I am running Ventura 13.3.1 (a) (22E772610a) and my Cache setting is set to 100GB. 

This topic has been closed for replies.

4 replies

Ian Lyons
Community Expert
Ian LyonsCommunity Expert
Community Expert
May 17, 2023

The Apple explanation for spinning beachball is "the spinning wait cursor is displayed automatically by the window server when an application cannot handle all of the events it receives". In short, the beachball is there to tell you your Mac is too busy with a task to respond normally. So, why do you see the spinning beachball?

 

The Camera Raw cache is only used for proprietary raw files (NEF, CR2, ARW) and the previews built during import aren't used by the Develop module. Therefore, even if your cache was 1000GB it wouldn't help. LrC is rendering each of your JPEGS from scratch as you scroll through them in the Develop module. In your case the JPEG files at 20GB each, which if you're scrolling (I assume via the filmstrip) means a file needs to be read from disk, rendered, etc. each time you move to the next image. Definitely not a workflow the Develop module in LrC was designed for. Best you use the Library module.

TheDigitalDog
TheDigitalDog
Inspiring
May 17, 2023

This may be a 'bug' (IOW need more optimization); others have reported this too. 

Develop will be slower 'walking' through images compared to Library due to the preview Architecture. You may wish to do this kind of viewing in the Library. 

Without getting into trouble, you should see this considerably faster in 'upcoming' versions; Adobe is working on optimization of this.  

Author “Color Management for Photographers" & "Photoshop CC Color Management/pluralsight"
DdeGannes
Community Expert
DdeGannesCommunity Expert
Community Expert
May 17, 2023

You need to use the Library Module to perform that task. Lightroom builds previews and uses them so you can view more quickly.

When you are using the Develop Module Lightroom has to render from the Original Images.

Regards, Denis: iMac 27” mid-2015, macOS 11.7.10 Big Sur; 2TB SSD, 24 GB Ram, GPU 2 GB; LrC 12.5,; Lr 6.5, PS 24.7,; ACR 15.5,; (also Laptop Win 11, ver 24H2, LrC 15.0.1, PS 27.0; ) Camera Oly OM-D E-M1.
S
Seaquence
Known Participant
May 17, 2023

I have very similar worflow obligations and have found the same problem with LR. Dont get me wrong, I love LR but just not to cull bulk images with. Im not exactly sure why this happens in the develop module but it could be because 1:1 previews are trying to load, or if your catalog is on an external HDD, your using usb2,  but as I said I'm not sure and one of the experts may be able to give you a better reason. One thing I do know for sure, is its faster culling in the Library module but unfortunately not as fast as external programs such as Photo Mechanic, which is what I use before importing the edit to LR. Saves me a lot of time.

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices