P: GPU used even if you deactivate it when exporting and confirm to LrC not to use it

[ouiouiphoto]

Dear all

Windows11

LrC 13.0.1

Step to reproduce. 

1) Activate GPU. Select several photos with development. Export them. Look at your resource monitor for GPU

2) Deactivate GPU. Restart Lightroom. Select the same photos. Launch the same export 

3) A warning message tells you that the GPU is deactivated and ask you if you want to activate to speed up export. Press cancel to keep it deactivated. Look at you resource monitor for the GPU. The GPU and GPU memory is used anyway

 Kind regards

[ouiouiphoto]

Hello @Rikk Flohr: Photography Any idea why this one has been moved to Discussions. As far as I remember, I have created it as a bug. And using GPU when you ask not to use it seems a bug to me no ? 

Kind regard

[Rikk Flohr: Photography]

Short answer 24/25 'bugs' posted to this forum do not turn out to be actual new bugs.  (2) are already reported and (~22) are not really a bug.  

Long answer: I attempted to replicate what you are seeing on your system with my Windows system and I do not see that bad behavior.  I cannot reproduce the behavior so it gets kicked to Discussions which has 10x the traffic of bugs to see if anyone else sees what you see. 

But, the most common answer for why bugs are moved is they simply lack the necessary information to even begin to attempt to reproduce. 

Additionally, Bugs is only for confirmed bugs who have a matching ticket in our bug tracking system. The goal is that if you see it in Bugs - you can bank on its being reported and triaged by the team. It is not a dumping ground for every bad behavior experienced.

[ouiouiphoto]

Thanks for your answer @Rikk Flohr: Photography 

If you follow this bug https://community.adobe.com/t5/lightroom-classic-bugs/p-artifacts-resembling-clipping-warnings-odd-b... you will see that deactivating the GPU is one solution. But some user has done it and the problem still exist in export. And my print screen explain why

Lets see if it is more useful in the discussion side of this forum

 Kind regards

[johnrellis]

[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]

I also observe that LR 13.0.1 uses the GPU for export regardless of the setting of Preferences > Performance > Use GPU.  But LR 12.5 obeys the setting for export.

As @ouiouiphoto points out, users on old Macs with no-longer-supported graphics drivers who are experiencing the "artifacts" problem are forced to roll back to 12.3, since disabling the GPU doesn't work around the problem with their exports.

LR 13.0.1, Off:

LR 13.0.1, Auto:

LR 12.5, Off:

LR 12.5, Auto:

[ouiouiphoto]

Hello @johnrellis thanks for your confirmation 

[johnrellis]

@Rikk Flohr: Photography, please consider moving this into Bugs -- I've replicated the problem on Mac (see above).

[Rikk Flohr: Photography]

The team has confirmed and we've logged a bug for the behavior. 

[Radim5EBC]

Observing exactly the same discussion. I mean bug. Waiting for reply. I mean fix.

[Spyth4514]

Same problem with my iMac late 2015 with AMD Radeon R9 M390 2gb using v13.02

Stuck on my work, please make something about it.

[EnergyPhotos]

I have the exact same problem. GPU is always used, no matter if i check it in preferences or not. 

I am looking at resource monitor and other hardware monitors, and i am 100% sure. 

In the past, checking or unchecking "use GPU for export" did make a big difference (off  = CPU ~100%, GPU 0%, on = CPU 40%, GPU 35%) 

[SYNDICATE Rob]

Interestingly enough, my GPU isn't being used at all on v13.0.x regardless of acceleration on/off. v12.5.1 was fine.

5900x, rtx 2080, 980 pro, 64gb RAM @ 3600.

Times to export 100 images to ssd:
v13.0.1 GPU OFF - 1:41.96 (20% avg cpu 55 deg)
v13.0.2 GPU OFF - 1:41.81 (24% avg cpu 55 deg)
v12.5.1 GPU ON export- 47.07
v12.5.1 GPU IP only - 53.46
v12.5.1 GPU FULL OFF - 53.24
v12.5.1 GPU FULL ON - 46.9
v13.0.2 GPU FULL ON - 1:39.93
v13.0.2 GPU FULL OFF - 1:40.39
v13.0.2 GPU FULL ON - 1:40.76

[EnergyPhotos]

Basically i believe this means GPU is used. And you have the same bug, 
You have same export speeds (more or less) regardless if use select GPU or NOT.

If GPU wasn't used you should see CPU usage close to 100% (or 90% if you have a bottleneck in HDD for example) and GPU usage close to 0%.
If GPU is used, the normal is to see both CPU and GPU around 30%.

so in version 13.x your speeds are basically the same regardless if you use GPU or not, and CPU usage is ~25% this indicate that this setting makes no changes. 
While in version 12.x this setting gave you almost 15-20% speed boost. (46sec vs 55sec) 

[SYNDICATE Rob]

I don't disagree, just odd seeing 0% on GPU stats

[Rikk Flohr: Photography]

Greetings all,

Updates for the Adobe Photography Products have been released.  The December 2023 updates contain an update for this issue. 

If you do not see the update in your Creative Cloud Application, you can refresh it by hitting [Ctrl/Cmd]+[Alt/Opt]+[ R ].

Note: It may take up to 24 hours for your update to be available in your Creative Cloud app.

Thank you for your patience.

[johnrellis]

In LR 13.1, I observe correct behavior: The GPU is not used for exporting raws when Preferences > Performance > Use Graphics Processor > Use GPU For Export is unchecked.

[Radim5EBC]

Issue seems to be fixed now, thanks

[.Michael.]

I reported an equal bug already in October and it was ignored!

[SYNDICATE Rob]

I'm starting to think a permanant rollback to 12.5 might be in my future, but that obviously creates some conflict with needing to access existing v13 catalogs.

The difference in export speed is just so staggering on my machine from 12.5 to v13 that I can't ignore it, with my average weekend export often topping 2k images.

[SYNDICATE Rob]

20k sorry. And permanent lol.

[johnrellis]

@SYNDICATE Rob, "The difference in export speed is just so staggering on my machine from 12.5 to v13 that I can't ignore it, with my average weekend export often topping 20k images."

You've posted in a thread about a bug that was fixed many months ago and very likely unrelated to your issue. Please start a new thread about your issue, including full details and full output from the command Help > System Info.