@Man Sorry, I completely missed this post in the thread - I think I must have skipped over it, as there was a delay between my post being made (in response to the post above yours) and it being approved by moderators and appearing below yours.
In response to your question, the GPU accelerated parts of the process should take the same time to process, per image, but not all of the work done during an image export is done on the GPU. The traditionally slower parts of the DeepPRIME noise reduction process are definitely offloaded to the GPU wherever possible, but for all I know, some parts of the process may not lend themselves well to GPU processing, so may still involve some CPU work.
Even if the vast majority of the DeepPRIME noise reduction process is now GPU accelerated, exporting an image, involves more than just DeepPRIME noise reduction. Colour and exposure adjustments, sharpening, compressing and exporting the JPEG etc. are all part of the export process as well, and even with OpenCL GPU assistance enabled for processing, the CPU still has some work to do. The DeepPRIME export process will be like a production line, with images in progress being passed back and forth between the CPU and the GPU in the background. If one is faster at doing its parts of the process than the other, itās going to spend some time idle, either waiting for the other one to provide it with more data, or waiting for the other to be ready to process the next piece of data it needs to give it.
Hopefully that makes sense. I expected something along these lines to happen in my testing, as I suspected my GPU wasnāt being used to its full potential before. Now Iāve had chance to run some tests, confirm my hypothesis, and get some rough numbers. I hope thatās of use to someone.