• Welcome to the Lightroom Queen Forums! We're a friendly bunch, so please feel free to register and join in the conversation. If you're not familiar with forums, you'll find step by step instructions on how to post your first thread under Help at the bottom of the page. You're also welcome to download our free Lightroom Quick Start eBooks and explore our other FAQ resources.
  • Stop struggling with Lightroom! There's no need to spend hours hunting for the answers to your Lightroom Classic questions. All the information you need is in Adobe Lightroom Classic - The Missing FAQ!

    To help you get started, there's a series of easy tutorials to guide you through a simple workflow. As you grow in confidence, the book switches to a conversational FAQ format, so you can quickly find answers to advanced questions. And better still, the eBooks are updated for every release, so it's always up to date.
  • 12 February 2025 It's Lightroom update time again! See What’s New in Lightroom Classic 14.2, Mobile & Desktop (February 2025)? for Feature updates, new cameras and lenses, and bug fixes.

Maximizing LR Classic Performance for DEVELOP (where vast majority of time spent, going bt photos back and forth to compare; making develop adjustment

Status
Not open for further replies.

cogden

New Member
Joined
Jun 10, 2015
Messages
6
Lightroom Experience
Power User
Lightroom Version Number
11.3.1
Operating System
  1. macOS 12 Monterey
Hello hive-mind,

The Apple Studio M1 Max vs ULTRA benchmarking articles have been rolling in. HOWEVER, the tests seem to focus on batch processes (eg, import/export) vs. Interactive function speeds where we spend most of our time (and are "chained" to the computer vs start export and walk away until finished).

Does anyone have data about maximizing LR Classic (LrC) Performance for DEVELOP (where vast majority of time spent, going bt photos back and forth to compare; making develop adjustments and waiting for LrC to render image (which is SLOW with 50-150mpxl raw files 30" monitors))? Ditto with searches in target catalogs (eg 650K images)? Ditto with add/delete collections speed (in 650K image catalogs w-lots of collections/sets)?

What matters most: CPU Speed, # Cores, GPU, Neural Engine, other?

(PS the Puget Sound benchmarks are interesting, but are for Windows and the https://www.dpreview.com/articles/6821380037/apple-m1-ultra-vs-m1-max-head-to-head-shootout article is helpful but seems to miss the boat re: DEVELOP Speed maximization. )
 
Hardware is not my wheelhouse, but FWIW…

The general principles of the Puget Systems ones should apply, even though it’s Windows based.

For previews and rendering, GPU use is growing so I’d put that as top priority, along with decent amounts of RAM since it’s shared on M1’s. Even more so with big monitors.

Searches and catalog stuff are generally more limited by drive speed, followed I think by single CPU speed.

I’m happy to be corrected if someone has better information.
 
Status
Not open for further replies.
Back
Top