DPP 4.18.10.0 Editing RAW files is really slow

[mysql]

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 :-).

[jrhoffman75]

---

@mysql wrote:

aah no no Ccleaner 😕 not my favourite app anny other suggestion? 🙂

---

It works for me. You will need to find your own.

[mysql]

ah never mind, still thank you 🙂

[fscotthopkins]

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

[mysql]

Those are really interesting finds and as you wrote we are on same boat, well I solved it by not using it at all... which in some case is a small problem as for example Focus Stacking worked great in it or when you have RAW burst set it only can be opened in DPP... so you get some and you loose some...

Cool you work with SQL 🙂

[fruitfly]

---

@fscotthopkins wrote:

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.

I was inspired by this post to open an account here and share some of my observations. I invested some time into trying the latest Lightroom and DxO Photolab versions, but liked DPP output more, so I am sticking with DPP. The question is - how can one make it faster, particularly for the editing process?

I completely agree that DPP seems to rely mostly on the CPU for the JPG conversion process and does not use the GPU much or at all. I also found that the use of RAM is not that extensive.

After I upgraded from EOS R to R6mkII I noticed a drop in processing speed in DPP. As an experiment, I ran a few tests by downloading RAW files of the same still life scene from Imaging Resource (trying to keep things as uniform as possible), then duplicated each file to get 5 identical copies, and ran batch JPG conversion in DPP. Here are the times (on a PC with i9-11900 processor):

Camera                Time for 5 files, sec         Time for 1 file, sec           Mpixels

RP                           35                                           7                                  26.2

R                             44                                           8.8                               30.3

R6                           70                                           14                                 20

R5                           148                                         29.6                              45

R6 mark II               87                                           17.4                              24

The main observation is that "something happened" when Canon moved from R/RP to R6, R5 and later cameras - processing times more than doubled for similar sensor size! (I tend to blame the new Clarity slider that wasn't there before - maybe there is more to it than that).

But my main quest has been to speed up the dreaded spinning wheel at the bottom right. (By the way, related to the results above, the wheel times are much faster for the R files compared to R6mkII, and still faster for older models) One surprising discovery is the following: I recently started using the Neural Network Processing tool, and found that screen updates/wheel times when working with .CRN files are ~3 times faster than when the corresponding .CR3 files are processed! This is despite the fact that the .CRN files are ~5 times larger. Now my workflow is the following:

I first cull the RAW files with FastStone (I find that this is faster than using DPP for the same task). Then I batch-process all .CR3 files into .CRN files using the Neural Network Processing tool in DPP, and only then make edits/adjustments. Neural Network processing is slow (for R6mkII it's about 45 seconds per file on my computer using 4060 Ti GPU), but I just start the batch and walk away (can do overnight), and then my editing after that is much faster. Also, the NNP tool does run on the GPU! I also like the output of this tool (had to reduce sharpness, otherwise it overdoes it). 

[fscotthopkins]

"But my main quest has been to speed up the dreaded spinning wheel at the bottom right." A windmill worthy of tilting at ... Has to be the most frustrating feature of DPP.

"I first cull the RAW files with FastStone (I find that this is faster than using DPP for the same task). " - Definitely the sort of tweak I was hoping someone might suggest. Thanks for this. It will help vanquish the dreaded wheel  so I will give this a try.

Your numbers between models make sense.  I'm quite sure Canon adds much more to process between each model. Makes sense to me now why I never really noticed the spinning wheel back when I was only pulling in raw files from a 7D.

"Then I batch-process all .CR3 files into .CRN files using the Neural Network Processing tool in DPP, and only then make edits/adjustments. Neural Network processing is slow (for R6mkII it's about 45 seconds per file on my computer using 4060 Ti GPU), but I just start the batch and walk away (can do overnight), and then my editing after that is much faster. "  -  I'm pretty sure the practice of starting a batch and going home ( or to sleep or watching a movie or ...????. ) goes back 60 years. I'm a hobbyist on shoestring so not quite ready to spring for the Neural Network Tool just yet.  After decades of managing batch processes, it's not much to work around.  I wish it would leverage the GPU to speed things up, but I suppose if it did, it would only be an ephemeral improvement until the next model produces images that take double the time to process.