cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

DPP 4.18.10.0 Editing RAW files is really slow

mysql
Contributor

Hello,

I have laster version of DPP 4.18.10.0 and when I want to try edit RAWs from my R6 Mkii it is hell slow, quick google search pointed me possible option to enable Use GPU processing but I don´t have this option in Preferences/Image Processing 2.

I have 1080Ti with lastest drives and I don´t think this is "slow or old" card (yes there are faster and newer ones but still).

So is it realy caused by old video card? 

Thanks for helping :-).

12 REPLIES 12

ah never mind, still thank you 🙂

and I am not even talking about using just DPP/Canon stuff - DualPixel Raw, Raw Burts, HDR PQ, HDR and all of those just DPP RAW things which are exclusive to DPP those are even slower

fscotthopkins
Apprentice

I found this thread while researching the speed of raw processing under DPP v 4.18 and trying to find settings to see if I could enable / leverage my GPU.  While I was hoping to find a "magic" setting or two to enable faster processing it did inspire some research I hope will contribute to the questions here and help others.

A little background: I'm currently using a laptop with Win 11, Intel i9-14900 24 core CPU, 40 GB Installed RAM, Intel integrated UHD Graphics (2GB), and Nvidia RTX 4060 Laptop (8GB).  I purchased the system in part due to my experience trying to process batches of 100 or more images using DPP 4 a couple times a year using my somewhat aged laptop from 2014.  I recently took a batch of 96 shots for a family holiday portrait using my R6 (mk1). All shots were taken using the same settings 1/200, f8, auto iso, flash indoors next to a wall of windows.  I used DPP v 4.18 to apply Auto Lighting Optimizer (Adj Face Lighting), set Daylight WB, and Portrait Picture style followed by Batch Processing to create 350 dpi jpgs. The process ran faster than my old laptop (about 27 minutes for all 96 images) but I was curious if I could find ways to improve the speed hence the reason I found this thread.  

Since previous comments confirmed my suspicion that DPP 4.18 doesn't provide a setting to leverage GPU I thought I could add a couple tests to determine if it DPP 4.18 would automatically leverage the GPU. 

This is what I found processing the 96 CR3s:

* There are no settings in DPP 4.18 for enabling or using GPU that show up based on operating system settings

* DPP 4.18 appeared to add maybe 3 GB to the memory allocation. Memory allocation without CPP was about 9GB but never went above 12 GB for any test.

* DPP 4.18 did not impact either the internal or external drive in a significant manner (other than reading and writing files)

* CPU utilization consistently saw-toothed between 10,50 ,100, and 75 percent for all tests

* Overall duration of processing did not vary based on any GPU settings or drive used (internal vs external)

Test 1 - CR3 files stored on (and output to) external Samsung T9 with automatic selection of GPU vs integrated Intel.  27 minutes

Test 2 - with all settings forcing Nvidia 4060 GPU. 27 minutes

Test 3 - CR3 files stored on internal SSD with all settings forcing Nvidia 4060. 27 minutes

Test 4 - CR3 files stored on (and output to) external Samsung T9 with all settings forcing integrated graphics (effectively disabling Nvidia GPU). 27 minutes

Test 5 - Just to see the difference, I copied 96 CR3 files my old laptop. Specs: Win 10 Intel i7, 2 cores, 12 GB RAM, Nvidia 840 (2GB), DPP 4.18 - 141 minutes

Conclusion: DPP 4.18 appears to rely heavily on CPU and RAM based processing without leveraging dedicated GPU hardware. My guess is this might be a strategy to produce software which runs on multiple platforms without the extra expense of integration to dedicated graphics processing hardware.

If anyone else has some benchmarks or thoughts I'd sure be curious what they've found. As for your original question mysql, I guess you and I are in the same boat.  BTW - great handle. My day job is SQL

 

 

 

Announcements