I just exported a bunch of mixed raw and jpeg photos into a local folder and it’s the first time I ever heard my MBP 14" M1 Pro fans working. CPU usage is up the roof!
The export files are from Fuji RAF and Jpegs. export to jpeg, resize to 3000px, 80 quality. Nothing major.
See Activity Monitor screen shot.
Is this normal?
Hmmm, this is not matching my experience with exporting raw files on a Mac Mini M1 (so it’s not even the Pro version if the CPU).
Export is fast and totally silent, even when DeepPrime is enabled.
Are you using the very newest version of PL5? I found the latest release to run far more smoothly and quickly on my machine (DxO said in the rease notes that all the code was optimised for the M1 in this release, older releases it wasn’t all there yet).
I’m running MacOS Monterey, but I’ve no idea if using an older version of the OS would affect exporting.
Also, I’m exporting Nikon NEFs which have had support within PL for a long time, so could this be related to the Fuji files you’re working with, for which support is still very recent?
PS my machine also only has 8Gb memory and a 512Gb SSD, so it’a definitely not to be considered a high end spec, so yours should (imo)be running quickly and quietly…
I usually don’t have CPU issues with PL5. I am using the latest version and OS.
I suspect this is a Fuji RAF support issue.
Do you have any live anti virus or malware packages scanning files on demand? Bit of a long shot. Mine are Leica DNGs to start with. I do not have this issue when exporting TIFFs or JPEGs on an M1 MacBook Air, and some of those TIFFs are pretty big if they’ve done a round trip through Topaz
No I don’t have any anti virus or maleware running.
That looks like when you are using CPU for export and not the Neural Engine or GPU.
Take a look under Settings/Advanced/DeepPRIME acceleration.
Set it to Auto or Neural.
It’s set to Auto Selection (Apple Neural Engine).
How many is a bunch?
If you take the same set and try again, does the problem persist (can you replicate the problem)?
I just ran it again. Same results. CPU goes nuts!
Just seen this post from 2021 about PL4, I’m away from my computer just now - is it still there in PL5? Other than that, you could always try the good old uninstall/ reinstall - might not get to the root of the problem but if it went away that may be enough
Bit out of ideas I’m afraid, I’m new to PL5 too
Just a thought …
Does the fact that your Activity Monitor is showing 5 separate instances of XPCCor indicate that you have specified for PL to “simultaneously process” that number of images (during Export) ?
If the Mac version has the ability to adjust this number (?), then you might try a lower setting …
- PL Win Version:
Regards, John M
It’s possible on Mac
and it looks like some difference in GUI
I don’t remember to which count I can set it on windows system and if depends on processor or RAM, but on my MB Air M1 with 8MB the maximum is 3
If CPU load is at 100%, this simply means that your CPU does all it can do, it wastes no cycles and puts everything into processing your images. You can’t get more than 100% of what is available, so getting 100% is the best you’ll get, which is a good thing, because it provides the shortest overall export times.
Depending on your customising and GPU capabilities, export load is also handled by the GPU, which can shorten (or lengthen) processing times.
To find the sweet spot with your computer and usual customising, change the number of parallel export processes as shown above and see how times vary vs. number of parallel processes. On my 8-core iMac, the best setting is 4. Sometimes, 3 or 5 would provide shorter export times, that’s why I leave settings at 4 - out of 12 (on iMac)
Background: Processing is limited by a) the CPU, b) the GPU and c) how fast bits can travel between CPU and GPU. Finding the sweet spot is to balance the trio (CPU, GPU, transfer) in a way to provide optimal load distribution and hence shortest processing time.
just for information, what’s the highest count of parallel processes you can set on your system?
Yes I can adjust the instances but really? something quite simple like rendering jpegs from a small batch on a M1 Pro chip should be a breeze. I’ve done far more complex exporting scenarios in my life without too much of a hassle. I will try running the same batch in LR and run similar complex mix using Canon files and see if that makes a difference.
This is me as well. same machine, same settings.
True - but if you have a high number specifiied then you’re instructing PL to run all those exports concurrently … which means that each thread is fighting others for resources.
Thanks @John-M I will try different setting and file types and will report back.
I tested PL with only two parallel processes and it took roughly 2 minutes to export 76 images and while the fans didn’t kick in the Mac became very hot.
The same export from LR took roughly 20 seconds!