![]() Since I usually run large batches of raw images, I start the process and then leave to have a coffee - I usually don’t have anything else running. ![]() (At least for my hardware - maybe it has more effect for lower end hardware.) On both systems, even with 8 images selected, DxO PL5 doesn’t come close to loading these systems anywhere close to 100% - so I doubt this adjustment has any significant effect to the performance of other apps running in parallel - macOS is going to handle the multi-processing. I have a set of 43 RAW images I use for testing - a mixture of Sony A7RM3 and M4, some Olympus E-M5III, and various (older) Canon Digital Rebel images. Both systems are fastest when processing 4 images. I benchmarked these two systems with the 8/4/1 image settings. I have an (Intel) iMac Pro with a Xeon W 8-core CPU and a MBP M1 Max with 10 cores (two efficiency, 8 performance). In each case, the app uses all the CPU cores. I have tested 8 images, 4 images, and 1 image options. I have been watching what is going on under different settings. ![]() ![]() But, the User Guide simply says that this is a way to control the impact of the DxO application on the system - you can reduce the load (if you want to run other apps at the same time) by reducing the number of images processed in parallel. I had assumed it controlled the number of CPU cores used by the application. I am trying to understand exactly what this preference does. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |