High prolonged CPU following completion of Denoise; Developer path in ACR DLL
I'm xperiencing the same problem as discussed in ACR Ver 17.0 Denoise AI - Strange High CPU use aft... - Adobe Product Community - 15018356
This occurs on both a DIY desktop and off-the-shelf laptop. Both are Win11 Pro. Desktop is i7-8700K with NVIDIA 3060TUF and the laptop is an I9 with an NVIDIA 4070, both fully patched with clean installs of current NVIDIA Studio drivers.
I extensively tried to debug by reinstalling Adobe software, clean install of graphics drivers, resetting prefs, toggling pref settings, clearing caches, etc.
The issue only occurs when GPUs are enabled, and only if edits have been made to the raw file, either because of applying an import develop preset or after import. A single edit (e.g., adjust exposure) causes high CPU for 3-4 seconds following completion of denoise. Multiple edits cause high CPU for a prolonged period of 1-2 minutes after denoise is complete, significantly interfering with my ability to move forward in my workflow. With GPU off, high CPU occurs only for 2-3 seconds following denoise.
Oddly, the actual time to denoise is 15 seconds regardless of whether GPU is enbled or off.
I used sysinternals tools to try to trace what was causing the performance hit when using the GPU. I noted that the CameraRaw.dll file contains many strings pointing to paths on what appears be Adobe development machines. Here's a sample of just one:
D:\workspace\release\15.0.1\lr-win-inst\classic-new\toolkits\image_io\source\GPUView.cpp
Now I haven't developed code in quite a while, but I think having absolute references to paths in the development environment included in a DLL running on a customer's machine is atypical, and I have to wonder if this is contributing to some of the anomalous performance behavior some of us are seeing.
AdChoices