M1 Max Lightroom Classic performance

[nihil0]

Did anyone have a chance to test the performacne of M1 Max CPU in Lightroom Classic? I saw this video by ArtIsRight where he compared 12-core 2019 Mac Pro with M1 iMac and the 1000 images import & export times were roughly 1 times slower on M1 than on 12-core Mac Pro (Import MP: 13m7s, Import M1 iMac: 24m25s, Export MP: 14m55s, Export M1 iMac: 27m27s). Now, is it safe to assume that since M1 has 4 performance cores and M1 Max 8 performance cores that the import & export times for those files would be on par with 12-core Mac Pro?

 

[andrewj]

While this may not be the most scientific comparison, I compared building 1:1 previews between my 2019 Intel 16” MBP 2.4 Ghz 8 core with 32 GB RAM with a max spec 16” M1 Pro Max with 64 GB RAM. For 127 files, it took about 3:24 on the older MBP and 2:32 on the newer MBP. So significantly faster. It also feels faster navigating in LR as well.

 

[nihil0]

Thanks for the reply. I put the approximate numbers into calculator an it would mean that on M1 Max it would take around 20 minutes for 1000 pictures 1:1 import. That is only 4-5 minutes faster than M1 iMac - I expected more performance actually, to be closer to 12-core Mac Pro, maybe like 16 minutes tops.

 

[quasibinaer]

The workflow nerd in me just reared its head and said that an import of 1000 images with 1:1 previews is most probably bad practice and should be avoided. I haven´t got the faintest idea why anyone would do that. I´d be interested in rendering speeds for standard previews on the 14" and the subsequent culling performance though...

 

[Pressure]

ArtIsRight also points out that Lightroom CC is utilising the hardware better than Lightroom Classic.

 

[wilberforce]

The workflow nerd in me just reared its head and said that an import of 1000 images with 1:1 previews is most probably bad practice and should be avoided. I haven´t got the faintest idea why anyone would do that. I´d be interested in rendering speeds for standard previews on the 14" and the subsequent culling performance though...

I quite often do this. I prefer to go get a cup of coffee while all the 1:1 previews are rendered, than have rendering lags when culling. I frequently zoom 100% when culling to check for sharpness, for which I need 1:1 rendering.

One disadvantage is my previews file is often several hundred GB

 

[nihil0]

The workflow nerd in me just reared its head and said that an import of 1000 images with 1:1 previews is most probably bad practice and should be avoided. I haven´t got the faintest idea why anyone would do that. I´d be interested in rendering speeds for standard previews on the 14" and the subsequent culling performance though...

I do that for every single wedding. Come home, download data from SD card, create new catalogue just for the wedding, load ALL the photos and then cull and apply edits. After I export edited photos and deliver them, I wait couple of weeks and then delete everything. So that is why I need fast raw processing power.

 

[nihil0]

ArtIsRight also points out that Lightroom CC is utilising the hardware better than Lightroom Classic.

Too bad Lightroom CC is crippled.

 

[wilberforce]

Too bad Lightroom CC is crippled.

Lightroom CC is gradually improving (like the new neural filters and masking layers), and I get inspired to try it again every Adobe Max, but then I keep going back to Classic. Can't deal with the file management limitations

 

[andrewj]

I do that for every single wedding. Come home, download data from SD card, create new catalogue just for the wedding, load ALL the photos and then cull and apply edits. After I export edited photos and deliver them, I wait couple of weeks and then delete everything. So that is why I need fast raw processing power.

Same here. I like having the 1:1 previews to minimize lag when scrolling through the photos.

 

[macphoto861]

Would be a potential game-changer if Adobe would implement GPU utilization for exporting JPEGs (like Capture One does).

Edit: and building previews too!

 

[nihil0]

Would be a potential game-changer if Adobe would implement GPU utilization for exporting JPEGs (like Capture One does).

Edit: and building previews too!

That would be awesome. Also, slightly off-topic: if they can implement AI subject select, they could do the same with faces only. Every other RAW processor has that.

 

[macphoto861]

That would be awesome. Also, slightly off-topic: if they can implement AI subject select, they could do the same with faces only. Every other RAW processor has that.

One thing I'd love to see (which they keep hinting around to in the surveys they've sent me over the past several years) is some kind of way to automatically identify and call to your attention quality issues based on the detection of faces. IOW, out-of-focus or eyes closed.

 

[nihil0]

One thing I'd love to see (which they keep hinting around to in the surveys they've sent me over the past several years) is some kind of way to automatically identify and call to your attention quality issues based on the detection of faces. IOW, out-of-focus or eyes closed.

That is also useful feature. And if they can identify faces regarding the quality issues, they can identify it and create mask only for the face as well.

 

[maxsquared]

Not benchmark per se, but I converted all my photos from Sony RAW to DNG, I did 500 per batch, the old Intel MacBook (i9 2.3 64GB) would heat up really quickly and it was pretty slow until the last 100 photos or so, then it ran really fast, but my new M1 Pro Mac (10/16/16 32GB) converts at the same speed as the last 100 photos the whole way through, and fan would kick off slightly and not loud, in fact that's the only time I heard the fan running.

In general use, the M1 is a lot smoother, especially zoom and adjustments.