Cyberpunk 2077 performance is reduced since commit bcfc25c9

[Sporif]

Cyberpunk 2077 performance is reduced, especially during holocalls.

Toggling the MangoHud overlay on during holocalls seems to increase the fps somewhat (but performance is still not at the expected level).

The commit that caused this issue is bcfc25c9.

Software information

Cyberpunk 2077, run with these graphics settings. I also have gamescope, ReShade, and MangoHud enabled but the issue still exists with all of them disabled.

System information

• GPU: AMD RX 7900 XTX
• Driver: Mesa 24.2.7
• Wine version: Proton 9.0-3
• VKD3D-Proton version: 2.13.r92.gcf34c0bd
• Distribution: Arch Linux
• Kernel: 6.11.8-1-custom

Log files

steam-14489251341945274368.log

These are performance logs taken using MangoHud with a holocall initiated in the middle of the run. You can see that the affected commit causes a drop in performance overall, but a severe drop during the holocall.

cf34c0bd: Cyberpunk2077_2024-11-14_19-35-45.csv
bcfc25c9: Cyberpunk2077_2024-11-14_19-40-33.csv

[doitsujin]

What is holocall?

Is there a way to visualize the CSV files or get any useful numbers out of them? What kind of performance delta are we talking about?

I don't really see why the commit in question would regress performance since it can't really pessimize synchronization compared to previous code (which had far more issues in that regard).

[mbriar]

Is there a way to visualize the CSV files

[doitsujin]

Need a fast way to repro in game then.

[Sporif]

Call any contact (they have to actually answer the phone). Usually one of the fixers will do.

[Blisto91]

Savegame where you have to do a holocall as soon as you load in for quick reproduction:
Cyberpunk holocall.tar.gz
Extract in to compatdata/1091500/pfx/drive_c/users/steamuser/Saved Games/CD Projekt Red/Cyberpunk 2077/

[doitsujin]

Can't reproduce with the savegame above, in both cases it's sitting at pretty much exactly 100 FPS when starting the call, tad more without the call. This is on a 6900XT with mesa-git from a couple of days ago.

[doitsujin]

Can reproduce now, but only when starting a new game with raytracing enabled.

[HansKristian-Work]

This seems related to a kernel performance bug on amdgpu. Guess we'll have to find a workaround ...

[HansKristian-Work]

This should be fixed now on master.

[Sporif]

Yes, it's fixed. Thanks!